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 #7495 set permissions on artifact priority change
Actions
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
4720

References
Artifact links
Empty
Referencing story #7495

Artifact Tracker v5

epic #7493 Sequence # in tracker and agile dashboard
rel #7843 7.11
request #7912 PHP generating errors from agiledashboardPlugin.class.php

Git commit

tuleap/tuleap/stable

Merge commit 'refs/changes/16/3616/9' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD 24ff97b654
User avatar Martin GOYOT (goyotm) , 2015-02-16 18:16
story #7495: Define a priority change permission on a planning (perms not taken into account) b7f3b4f4b9
User avatar Benjamin Dauton (bdauton_enalean) , 2015-02-13 17:19
Merge commit 'refs/changes/17/3617/13' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD 9a7c47690c
User avatar Martin GOYOT (goyotm) , 2015-02-16 18:22
story #7495: I can't reorder items in the content if I don't have the permission to do it d2d3976d20
User avatar Benjamin Dauton (bdauton_enalean) , 2015-02-13 18:55
Merge commit 'refs/changes/27/3627/11' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD 296a0909d9
User avatar Yannis ROSSETTO (rossettoy) , 2015-02-18 09:45
story #7495: Manage the perm in the planning v2 2213e5707b
User avatar Benjamin Dauton (bdauton_enalean) , 2015-02-17 17:32
Merge commit 'refs/changes/41/3641/2' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD fab75d6bc7
User avatar Yannis ROSSETTO (rossettoy) , 2015-02-18 09:52
story #7495: Prevent adding element in the backlog in planning v2 if user hasn't the perm to prioritize items 33175a14c8
User avatar Benjamin Dauton (bdauton_enalean) , 2015-02-17 17:33
Merge commit 'refs/changes/34/3634/6' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD 4e46b8c33d
User avatar Yannis ROSSETTO (rossettoy) , 2015-02-18 14:38
story #7495 - Manage the perm in the planning v1 399f0908e0
Martin Goyot (Erwyn) , 2015-02-18 12:26
Merge commit 'refs/changes/44/3644/3' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD b21712bbf3
User avatar Yannis ROSSETTO (rossettoy) , 2015-02-18 15:15
story #7495: Manage the perm in REST routes 69dc9a49d4
User avatar Benjamin Dauton (bdauton_enalean) , 2015-02-18 15:06
Merge commit 'refs/changes/52/3652/1' of http://gerrit.tuleap.net/tuleap into tuleap-stable-master 30746aad4b
User avatar Manuel Vacelet (vaceletm) , 2015-02-19 10:43
story #7495: Update REST api version 74cd2dbc49
User avatar Benjamin Dauton (bdauton_enalean) , 2015-02-19 10:33
Merge commit 'refs/changes/51/3651/4' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD ec71cffc98
User avatar Yannis ROSSETTO (rossettoy) , 2015-02-20 10:41
story #7495 - Tell the user why he can't drag'n'drop items 7c55bbc0a6
User avatar Martin GOYOT (goyotm) , 2015-02-19 16:44
Merge commit 'refs/changes/54/3654/1' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD 9771af42e2
User avatar Benjamin Dauton (bdauton_enalean) , 2015-02-24 14:22
story #7495 - permissions on static groups are not kept during duplication 05fcea5d2a
User avatar Martin GOYOT (goyotm) , 2015-02-20 14:53
Display settings

Follow-ups

User avatar
Manuel Vacelet (vaceletm)2015-02-06 10:44

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
Manuel Vacelet (vaceletm)2015-02-05 11:56
  • 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