Part of story #16125 [release management] create a new Aggregator Release Preconditions for tests: - Create projects (for example start from the Scrum template) - Install and activate the Multi Project Backlog plugin - Forge your database to define Aggregator and Contributor projects INSERT INTO tuleap.plugin_multi_project_backlog_contributor_projects (aggregator_project_id, contributor_project_id) VALUES (<id>, <other id>); In all projects, check all following conditions: - There is a top planning (e.g. Releases). - The Title, Description, TimeFrame and Status semantics are defined and use the same types of fields (for TimeFrame, they all use start / end date for example). - All contributor projects use at least the same values for Status field as Aggregator project. (They can have additional values). - The fields linked to this description are all submittable. - There is no workflow or date rules or list rules on synchronized fields (the semantics above). - Only title field is required (this will change in later commits). When all these checks are valid, the "Add new Releases" button will appear in Planning view of the Aggregator Project. If they are not valid, the button does not appear. ----- How to test: - Create a new release in the Aggregator Project. - "Mirror" releases should be created in each corresponding Contributor Project. They should have the same title, the same "Submitted on" date and the same "Submitter" user. Notes: - There is not yet an artifact link between the "Source" Release and its Mirror Releases. This will be done later. - Only the title field is mirrored for now. Other fields will come later. Change-Id: I1e9fb066f51f5f15d36ab5e70ea5c0cc141854a8

+1450 −17

Author

Joris MASSON (jmasson) 2020-09-22 10:59

Committer

Joris MASSON (jmasson) 2020-09-25 16:16

Hash 890359522cced2b92b45987c41edbde4bfd0833c

Parent 80aaa559722ff3bfec47d42d6003e0443c40f8cc

Reference git #tuleap/stable/890359522cced2b92b45987c41edbde4bfd0833c