Easy and mistake-proof way to map products for Rules
User Story
As a Catalog Manager I want an easy and mistake-proof way to map a Product in one family, to another Product in another family that has variants so that it will take that mapping and create a variant product which the Rules copying mechanism will use to copy the rest of the attributes over.
Background Documents
Ideas we had:
- Use a specific type of Association, so the user associations the Product (in a family with no variants) to a Product Model
- Use a special field in the Product to give an ID of the Product Model - either text or more mistake-proof a drop-down that is automagically filled.
Acceptance Criteria
(Describe additional criteria that must be met for the User Story to be complete)
e.g.
Whenever the user clicks cancel or tries to go forward or back in the browser they should be asked to confirm before they lose changes. If the user clicks Save any input should be validated so they can't make a mistake
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 -
Changelog is updated