•  
     
    story #16124 [release management] ensure Aggregator release creation is possible
Summary
Empty
[release management] ensure Aggregator release creation is possible
Empty

On Aggregator project, there is a "Create <Release>" button if

  • There is a higher level planning in each Contributor project and the aforementioned Aggregator project with a target tracker that have:

    • Title semantic

    • Status semantic

      • All values defined in the Aggregator project exists in all the Contributor project (duck typing)

      • All the "Open" values defined in Aggregator project are defined as "Open" in Contributor projects as well

    • Description semantic

    • Timeframe semantic

      • Aggregator & Contributor projects are using the same TimeFrame strategy (either start date + end date or start date + duration but not a mix)

    • An artifact link field

  • The current user (Program Manager) has the permission to create an artifact in all required trackers (Aggregator & Contributor)

  • The current user (Program Manager) has the permission to "Submit" all fields that need to be synchronized

  • The current user (Program Manager) has the permission to "Submit" and "Update" the artifact link field in all required trackers (Aggregator & Contributor)

Empty
Empty
Status
Done
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?

* Collect all configuration "errors" and add them in a log file (easy to debug)

* Check perfs

Details
#16124
Manuel Vacelet (vaceletm)
2020-09-04 14:56
2020-07-21 15:50
3667

References
Referencing story #16124

Git commit

tuleap/tuleap/stable

Follow-ups