Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

  •  
     
    story #17882 define cross project hierarchy between Features and User Stories
Actions
Summary
Empty
define cross project hierarchy between Features and User Stories
Empty

At this stage, it's only the REST route that will allow to associate:

  • one of the tracker defined in the Program Planning backlog (see story #17880) eg. Features or Enablers
  • to one of the backlog tracker of the higher level planning of Teams eg User Stories, Bugs, Enablers

This will configure the tracker hierarchy and we need to verify that everything is working as expected:

  • When a User story is linked to a Feature, the link "_is_child" must be created (and the other way around)
  • The display of parent in artifact view is done (even if there is no visual clue about the "other project")
  • The display of parent in Agile Dashboard Planning and Overview is done (even if there is no visual clue about the "other project")
  • Permissions apply

The read only administration UI has no longer meaning at this stage, it must be removed

Empty
Empty
Status
Empty
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?
Empty
Details
#17882
Manuel Vacelet (vaceletm)
2020-12-04 10:03
2020-10-16 16:13
3396

References
Artifact links
Empty
Referencing story #17882

Artifact Tracker v5

epic #16683 Program Management
rel #16653 12.3

Git commit

tuleap/tuleap/stable

Remove read only administration UI e1decf0efa
User avatar Thomas Gerbet (tgerbet) , 2020-11-19 15:14
PUT scaled_agile_program/{id}/hierarchy aee54e2d2f
User avatar Marie Ange Garnier (marieange) , 2020-11-20 11:18
route PUT /hierarchy should accept top plannable tracker and not top backlog tracker 845e0bcd91
User avatar Marie Ange Garnier (marieange) , 2020-11-20 15:45
Block PV2 access if program permissions are incorrect 7bce27b960
User avatar Marie Ange Garnier (marieange) , 2020-11-26 13:51
Program is always blocked with incorrect configuration message fd292e1478
User avatar Marie Ange Garnier (marieange) , 2020-11-30 11:08
Program is always bloacked with incorrect configuration message 5742e6c012
User avatar Marie Ange Garnier (marieange) , 2020-11-30 10:27
Block hierarchy management in the tracker admininistration for trackers involved in a scaled agile hierarchy 51f73da640
User avatar Thomas Gerbet (tgerbet) , 2020-11-30 11:06
Do not crash when looking at the hierarchy of a tracker with cross-project children 7413ec848d
User avatar Thomas Gerbet (tgerbet) , 2020-11-30 14:41
Block hierarchy of trackers involved in a scaled agile hierarchy (for real this time) 703628c5b6
User avatar Thomas Gerbet (tgerbet) , 2020-11-30 14:23
Hierarchy can be defined in more than a team project b7df5fb5a5
User avatar Marie Ange Garnier (marieange) , 2020-12-04 09:16
Display settings

Follow-ups

User avatar
Manuel Vacelet (vaceletm)2020-11-09 11:55
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
Manuel Vacelet (vaceletm)2020-11-09 11:32
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
Marie Ange Garnier (marieange)2020-11-03 10:52
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes