Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
pcmt
pcmt
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 152
    • Issues 152
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 0
    • Merge requests 0
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • pcmt
  • pcmtpcmt
  • Issues
  • #806

Closed
Open
Created Mar 04, 2021 by Josh Zamor@joshzamorOwner0 of 10 tasks completed0/10 tasks

Product Copy rule: attribute mapping used in script

User Story

As a SysAdmin I want the same attribute mapping present in Family to Family rule in the Product Copy rule so that I can define the same types of mappings, with the same behavior, in the different ways Family to Family rule's work.

Background Documents

(Insert links to any relevant documents)

Acceptance Criteria

  • Copy products rule is using attribute mapping in the processing
  • Where possible, we should have backend services used by both copy products rule and family to family rule.

Definition of Ready

  • User Story can be broken down no further
  • Acceptance Criteria and Story Points are agreed upon by development team and PO

Definition of Done

  • If required, UI Mockups are created and reviewed
  • Code is written with automated unit tests, reviewed, merged to master branch, all tests pass
  • All UI texts are multilingual
  • Manual tests in test environment are successfully performed
  • Test Plan is updated
  • Documentation is updated
Edited Mar 05, 2021 by Piotr Borek
Assignee
Assign to
sprint 47
Milestone
sprint 47 (Past due)
Assign milestone
Time tracking