•  
     
    story #7495 set permissions on artifact priority change
Summary
tracker user
set permissions on artifact priority change
I get a better control of who is allowed to raise/decrease priorities in my backlog

General approach

This story is meant to address the following needs:

  • One or several Product Owners of "Upper backlog" are allowed to change priorities at higher level
  • At "lower level" (for instance, sprint backlog), developers are allowed to change priorities but this should be limited to the scope of the sprint
  • The change at sprint level do have an impact at release or product level (if Story A is moved before Story B in a sprint, it will also be the case at Product level) but the changes are limited to the stories that are part of the sprint

Acceptance criteria:

  • Permissions are managed at Planning level
    • Each planning (Product, Release, Sprint, ...) has a group of people allowed to change priorities
    • By default, project members are allowed
    • The permission is exported/imported with XML template
    • The permission is inherited on project clone
  • Permissions are applied on cascade according to hierarchy. Example:
    • "product_owners" group has "priority change" permission on Release backlog
    • "scrum_masters" group has "priority change" permission on Sprint backlog
    • Release is parent of Sprint
    • Then, "product_owners" can change priorities in both Release and Sprint backlogs
    • But "scrum_masters" can only change priorities in Sprint backlog
  • The permission that apply on first planning (example Product planning when you have Products -> Releases -> Sprints) also apply on Project backlog (aka. Top Backlog)

Edge cases:

  • When dashboard is configured to manage 2 kind of children, like:
    • Product (backlog types: story, note)
      • Release (backlog type: story)
      • Info (backlog type: note)
    • With 3 plannings:
      • Product planning: manage "story" and "note" in "Product"
      • Release planning: manage "story" in "Release"
      • Info planning: manage "note" in "Info"
  • Then, permissions on both Release planning and Info planning are required to rank stories or notes in Product backlog
Empty
thomas.m.muller@ericsson.com, Patricia Carrasco (pcar), Emilio Palmiero (empa)
Status
Empty
Done
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [x] 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
#7495
Manuel Vacelet (vaceletm)
2015-02-24 16:22
2014-09-30 18:09
4719

References
Referencing story #7495

Git commit

tuleap/tuleap/stable

Merge commit 'refs/changes/16/3616/9' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD 24ff97b654
story #7495: Define a priority change permission on a planning (perms not taken into account) b7f3b4f4b9
Merge commit 'refs/changes/17/3617/13' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD 9a7c47690c
story #7495: I can't reorder items in the content if I don't have the permission to do it d2d3976d20
Merge commit 'refs/changes/27/3627/11' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD 296a0909d9
story #7495: Manage the perm in the planning v2 2213e5707b
Merge commit 'refs/changes/41/3641/2' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD fab75d6bc7
story #7495: Prevent adding element in the backlog in planning v2 if user hasn't the perm to prioritize items 33175a14c8
Merge commit 'refs/changes/34/3634/6' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD 4e46b8c33d
story #7495 - Manage the perm in the planning v1 399f0908e0
Merge commit 'refs/changes/44/3644/3' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD b21712bbf3
story #7495: Manage the perm in REST routes 69dc9a49d4
Merge commit 'refs/changes/52/3652/1' of http://gerrit.tuleap.net/tuleap into tuleap-stable-master 30746aad4b
story #7495: Update REST api version 74cd2dbc49
Merge commit 'refs/changes/51/3651/4' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD ec71cffc98
story #7495 - Tell the user why he can't drag'n'drop items 7c55bbc0a6
Merge commit 'refs/changes/54/3654/1' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD 9771af42e2
story #7495 - permissions on static groups are not kept during duplication 05fcea5d2a

Follow-ups

User avatar

The pending questions are on the connection between priority raise/decrease permission and items planning (drag from backlog and drop into a milestone):

  • Given the permissions described in acceptance criteria, "product_owners" should be allowed to plan any items at any level (Product, Release, Sprint). The should also be able to unplan (ie. move an item from milestone back to backlog)
  • But what about "scrum_masters" ?
    • Is it acceptable to not let them pick items from Release planning into Sprint planning (only Product owner would be allowed to do that) ?
    • Or do we want them to be able to pick items from Release planning but without having the right to change priorities in Release backlog ?

  • CC list set to thomas.m.muller@ericsson.com, Patricia Carrasco (pcar), Emilio Palmiero (empa)
User avatar
  • So that
    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
  • 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