•  
     
    story #10144 remove backlog hierarchy in favor of artifact link type
Summary
Empty
remove backlog hierarchy in favor of artifact link type

I have a flexible organisation of my work items

  • Underlying SQL queries should rely on "_is_child" instead of Tracker Hierarchy to look for children.
  • There is a new artifact link type "has_backlog" that allow to identify what is the Backlog of a given milestone. This replace the implict link bewteen planning & hierarchy
    • Until now in order to decide what to display as backlog of a milestone we add to look for
      • Artifact links of the milestone
      • Filter this list based on "Allowed Backlog trackers" of the corresponding planning
      • Display only what is allowed to be planned in submilestones (for instance when release is holding epics but sprint only accept user stories as backlog items. AKA the nightmare to manage)
    • With "has_backlog" and Scrum v2, to decide what to display as backlog of a milestone:
      • We look for artifact links with "has_backlog" type (with milestone as source)
  • The "has_backlog" type is added to all Agile Dashboard (even Scrum v1) - TODO: verify if it's manadatory to apply to scrum v1 or if it's easier to keep 2 separated execution paths: one without has_backlog, one with);
    • the consistency in Scrum v1 is ensured be Tracker Hierarchy and Planning Configuration
    • the consistency in Scrum v2 is ensured by Planning interface

Impact on "Planning view" drag'n drop

Warnings:

  • When a solo item is added as child of another backlog item, the "has_backlog" link of the milstone is removed AND the "has_backlog" link on all parent milestones must be removed recursively as well.
  • When a solo item with children is added as child of another backlog item, the "has_backlog" link of the milestone is removed AND all its children must also be removed from the milestone and sub-milestones recursively.
  • When a backlog item is removed from a milestone, all its children must also be removed from the milestone and sub-milestones recursively.
  • When a child is removed (to become a solo item) we must create the "has_backlog" link with the milestone AND the "has_backlog" link on all parent milestones must be created recursively as well.
  • When an element (eg user story) is create directly in a sub milestone as solo item we must create the "has_backlog" link with the milestone AND the "has_backlog" link on all parent milestones must be created recursively as well.

Impact on Carwall

Cardwall queries must be rewritten to take into account:

  • is_child link for cards children
  • has_backlog for cardwall swimlanes & solo items

 

 

Empty
Status
To be done
Development
Empty
Empty
Details
#10144
Manuel Vacelet (vaceletm)
2017-04-20 15:43
2017-04-13 11:28
3954

References

List of items referenced by or referencing this item.

Artifact Tracker v5

Follow-ups

  • User avatar
    • Acceptance criteria
  • User avatar
    • Acceptance criteria
  • User avatar
    • Acceptance criteria
    • Attachments scrum-v2-solo-to-parent-cases.png added
  • User avatar
    • Acceptance criteria
  • User avatar
    • Acceptance criteria
    • Attachments scrum-v2-remove-from-milestone.png added
  • User avatar
    • Acceptance criteria
  • User avatar
    • Acceptance criteria
    • Attachments scrum-v2-solo-to-parent.png added
  • User avatar
    • Acceptance criteria
  • User avatar
    • So that
    • Acceptance criteria
    • Attachments scrum-v2-stories.png, scrum-v2-epic.png added
    • Permissions set to