Restrict moving user stories around

Hello guys,

I searched on google, and seems the edit issues / schedule issues are responsbile for the ability to move user stories around. but i'm very relectint to edit the permission. it's not clear to me what those do.

Edit issue indicate to me at least the ability to add descriptions, change the subject, add lables and basiclly do all that you can do as editing of an issue?

I only simply want users except PO to not be able to move an item from the product backlog to an active sprint. i still want them to be able to move issues - other than user stories - to other (not active sprints) 

I do not want any other issue permissions stuff to be impacted !

Thanks,

1 answer

1 accepted

2 votes
Accepted answer
Tarun Sapra Community Champion Aug 07, 2017

Hello Ahmed,

From the docs -

  • Restricting users from Ranking issues — Only users with the Schedule Issues and Edit Issues Project Permissions  are allowed to modify the Rank of issues in the backlog. If you would like to prevent users from doing this, restrict their Schedule Issues permissions.
  • Restricting users from adding/dragging issues into sprints — Only users with the Schedule Issues and Edit Issues Project Permissions can add/drag issues into sprints. If you would like to prevent users from doing this, restrict their Schedule Issues and/or Edit Issues permissions.

Thus, currently ranking and drag/drop of issues is dependent on "Schedule Issues and Edit Issues " permissions only

Also, since you have mentioned that 

 i still want them to be able to move issues - other than user stories - to other (not active sprints) 

Currently, in JIRA the permissions are events on actions(edit, move etc) they can't be configured based on issueType. Though by using some clever scripting and some other plugins you can implement some restrictions based on issueType. But implementing restrictions on drag and drop which don't exist out of the box would hamper the user experience.

Dear Tarun, 

thanks for the answers. We have a similar problem:

  • Only PO should be able to prioritize the Backlog.
  • But all team-members should be able to prioritize their sub-tasks below their stories (i.e. prioritize sub-tasks on the Sprint-Board).

From the above I understand that the ranking permission cannot be bound to e.g. a board or a "context" like "Sprint" or "Backlog". From the above I understand that it would rather work by giving the PO the right to use ranking for ALL issue types and for all other team-members give the right for all issue types of "Edit Issues" but only for the Issue-Type "Sub-Task" to "Schedule Issues".

Did I understand it correct?

We are using JIRA-Server 7.9.2.

Thanks and Best Regards, 

   Bertram

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,752 views 18 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you