Looking for a way to only let admin/specific user move issues into started sprints in JIRA/GreenHopper.

[Antonio Khazdozian]

Essentially looking for a way to 'lock' started sprints and prevent all but selected users (in this case admins) to move issues into them.

Any other users would be able to move issues into sprints as long as said sprints have not been started.

Is there a way to do this?

Thanks.

[Theinvisibleman · Accepted solution]

Hi Antonio,

Currently I don't think it's possible to 'lock' started sprints, and all the users who have the 'Edit Issues' permission would be able to insert issues into the sprints. However, I agree that this would be rather useful to have, hence I have raised an improvement request for this here - JRA-32334.

For now, I would recommend that you do the following on the feature request ticket :

* Vote, so that it will receive more attention

* Watch it, so that you will receive any and all updates

* Comment, and give your opinion on the matter

Please note that the implementation of new features and improvement requests falls under [Atlassian's Implementation of New Features Policy|https://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+Policy].

[Rory Bernard]

Joanne,

basically (my take on this not Antonio's) is I want users to edit issues (inc. comments), manage the prioritisation in the backlog and future sprints but they should not be able to add anything to the currently open sprint. However, it would be useful for them to be able to comment on issues that are in the sprint.

Rory

[JoanneA]

Hi Rory,

I can totally understand that :) at the moment unfortunately it just isn't possible but please do vote and comment on the issue that Joe mentioned.

[JoanneA]

Hi Antonio,

You can remove "Schedule" permission for the users you want to restrict from changing the rank of an issue, however this prevents them from ranking any issues at all. At the moment you can't give them permission to only rank issues in the backlog and not current sprints.

Removing this permission means they can no longer edit the due date, but they can still edit issue details.

[Rory Bernard]

Bit of glaring omiision this one. Just missed an entire release deadline as one of the idiot users promoted a non-sprint issue to the top of the current sprint, got actioned by developers before it was spotted and now the release is missed. If I want users to describe their issues they have the ability to act as the Sprint manager as well - bad bad juju