•  
     
    story #10143 add/remove backlog items in planning view
Summary
product owner
add/remove backlog items in planning view
Empty

This story initialize the work on explicit backlog management. It focus on top backlog and under the hood work to put things in place.

Details

Enable the explicit backlog management

  • Agile Dashboard admin is converted to burning parrot (finish @bdauton contrib, the blocking point for bot mattermost can be simplified to text field)
  • In the section "Scrum", there is a switch that allows admin to opt-in explicit backlog management. At this stage:
    • the switch is one way only (it's not possible to switch back to implicit backlog management)
    • the backlog is created empty (even if there are stories/epics/activities that where "there" in the backlog, they are not automatically added to top backlog)
    • those 2 items might be re-considered in a later story if useful.

The explicit backlog management is handled in backend with a table "project_id|artifact_id". The option to implement that as a new field was evaluated. Once sobber again, it was decided to make it simple.

Use explicit backlog management in planning view

  • When an item is added to the backlog, the explicit link is created
    • Update PATCH /projects/:id/backlog implementation for "add" action
  • Items are listed in the backlog part of the view
    • Update GET /projects/:id/backlog implementation (this is the major part of the change in term of implementation)
  • In the card actions, there is a new entry "Remove from backlog"
    • Update PATCH /projects/:id/backlog to add a "remove" action
  • When a card is moved from backlog to milestone, the "top backlog link" is removed
    • From an implementation stand point this must be managed at Artifact Link creation level. When a backlog item is added to a Milestone, it is removed from "top backlog" table.
  • When a card is moved from milestone back to backlog, the "top backlog link" is (re) created

The assocation project_id,artifact_id is removed when an artifact is moved into a milestone. Another way to see it is that there is "global belonging to scrum realm" information stored in the database. From an implemenation point of view, to know if an artifact "belongs to scrum realm" we would need to check if it belongs to top backlog or a milestone.

Permissions

There is a change in permissions that applies for creation of backlog items. Until now, the ability to create artifact in the corresponding tracker was taken into account.

With this story, the ability to create (and remove) backlog items is inherited from the (already existing) right to prioritize elements in a planning.

Note: from a user of planning view PoV, nothing change as it was already impossible for someone who was not authorized to rank top backlog to create element. However until now it was possible to workaround that by creating the element directly in the corresponding tracker.

Change of data model

  • Planning/Hierarchy

    • When a tracker is removed from Backlog Item hierarchy or when it's removed from the "Backlog" part of a planning, the "top backlog" flag is cleared in database.

  • Copy/Move artifact

    • The new artifact is not linked to top backlog
  • Delete artifact
    • The link is removed
Empty
Laurent CHARLES (lcharles)
Status
Done
Development
Empty
  • 1 new REST route to remove element from top backlog
  • 1 new entry in "backlog item" menu to remove from top backlog
  • In XML import, in <agiledashboard> add list of top backlog item list
Details
#10143
Manuel Vacelet (vaceletm)
2019-11-08 08:45
2017-04-13 11:15
14307

References

List of items referenced by or referencing this item.

Git commit

Follow-ups

  • User avatar
    gerrit #16649 integrated into Tuleap 11.7.99.122

    • Status changed from On going to Done
  • User avatar
    gerrit #16640 integrated into Tuleap 11.7.99.106
  • User avatar
    gerrit #16638 integrated into Tuleap 11.7.99.103
  • User avatar
    gerrit #16630 integrated into Tuleap 11.7.99.96.
  • User avatar
    gerrit #16608 integrated into its repository
  • User avatar
    gerrit #16607 integrated into Tuleap 11.7.99.82
  • User avatar
    gerrit #16585 integrated into Tuleap 11.7.99.73
  • User avatar
    gerrit #16583 integrated into Tuleap 11.7.99.72
  • User avatar
    gerrit #16584 integrated into Tuleap 11.7.99.60
  • User avatar
    gerrit #16575 integrated into Tuleap 11.7.99.55
  • User avatar
    gerrit #16578 integrated into Tuleap 11.7.99.50
  • User avatar
    gerrit #16579 integrated into Tuleap 11.7.99.49
  • User avatar
    gerrit #16576 integrated into Tuleap 11.7.99.48
  • User avatar
    gerrit #16572 integrated into Tuleap 11.7.99.47
  • User avatar
    gerrit #16561 integrated into Tuleap 11.7.99.45
  • User avatar
    gerrit #16571 integrated into Tuleap 11.7.99.43
  • User avatar
    gerrit #16567 integrated into Tuleap 11.7.99.41
  • User avatar
    gerrit #16556 integrated into Tuleap 11.7.99.39
  • User avatar
    gerrit #16553 integrated into Tuleap 11.7.99.38
  • User avatar
    gerrit #16552 integrated into Tuleap 11.7.99.35.
  • User avatar
    gerrit #16551 integrated into Tuleap 11.7.99.33
  • User avatar
    gerrit #16548 integrated into Tuleap 11.7.99.32
  • User avatar
    gerrit #16544 integrated into Tuleap 11.7.99.30
  • User avatar
    gerrit #16543 integrated into Tuleap 11.7.99.28
  • User avatar
    gerrit #16542 integrated into Tuleap 11.7.99.27
  • User avatar
    gerrit #16516 integrated into Tuleap 11.7.99.23
  • User avatar
    gerrit #16518 integrated into Tuleap 11.7.99.22
  • User avatar
    gerrit #16514 integrated into Tuleap 11.7.99.17

    • Status changed from To be done to On going
  • User avatar
    • Acceptance criteria
  • User avatar
    • Acceptance criteria
  • User avatar
    • Acceptance criteria
  • User avatar
    • I want to
      -add backlog items to top backlog 
      +add/remove backlog items in planning view 
    • Acceptance criteria
  • User avatar

    The original content of the story moved as a epic #13997. This story is re-purposed with narrower scope.


    • I want to
      -manage backlog explicitely 
      +add backlog items to top backlog 
    • Acceptance criteria
    • CC list set to Laurent CHARLES (lcharles)
  • User avatar
    • Acceptance criteria
  • User avatar
    • Acceptance criteria
  • User avatar
    • Acceptance criteria
    • Technical informations
  • User avatar

    Good point, I added it to the story.


    • Acceptance criteria
    • Permissions set to
  • User avatar
    There must also be an ability to remove an artifact from the top level backlog. This may be needed when an item is no longer valid and does not need to be planned.