Family to Family rules: UI clarifications
User Story
As a SysAdmin I want some of the labels used in Family to Family to be changed so that I understand them better.
(weak story, I know, but it's easier to frame it as a story than track detailed issues)
Acceptance Criteria
-
Re-title the Pcmt Family to family rule
rule toFamily Copy by Attribute
-
Re-title the Pcmt Copy Products rule
rule toFamily Copy by Association
-
To the Family Copy by Association
rule properties page, add user instructions that say:Copy attributes from the source family to the destination family by using the association type <ASSOCIATION TYPE> that associates a product in the source family to the destination. This rule will create missing products, or intermediate sub-product models where they do not exist by using the mapped attributes to the destination family variant axis.
-
To the Family Copy by Attribute
rule properties page, add user instructions that say:Copy attribute values from the source family to the destination family by way of matching the value of the Key Attribute between source and destination products. The destination products must exist prior to copying.
-
Re-title the Pcmt Select options rule
toSet Select Attribute from Family
-
Re-title the Pcmt Pull images rule
toSet image from URL
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 by Piotr Borek