Restricting Fix Version

[Mark Stocker]

We are using Scrum so rank all our user stories to create the backup. When we plan a sprint we create a version and on the planning board we drag the Jira into the right version for the sprint.

Doing this adds the right sprint name/version to the Fix Version field in Jira. I would like the ability for certain team leads to assign Jiras to different Fix Versions but for everyone else that field should be read-only.

How can I set security for that field?

[Renjith Pillai · Accepted solution]

@Jobin, is it resolve issue permission or 'Schedule Issue Permission' (as per GH documentation here http://confluence.atlassian.com/display/GH/Scheduling+and+Assigning+Issues+in+GreenHopper) ?

[Renjith Pillai]

Oh really! I was thinking that the schedule permission is what matters all these while :(

[Jobin Kuruvilla [Adaptavist]]

If you go with the name, it is the 'Schedule permission' that makes more sense. But there u go :)

[Jobin Kuruvilla [Adaptavist]]

From JIRA Docs:

Schedule Issues

Permission to schedule an issue — that is, set and edit the 'Due Date' of an issue.

Resolve Issues

Permission to resolve and reopen issues. This also includes the ability to set the 'Fix For version' field for issues. Also see the Close Issues permission.

I have tested it and it is right. Seems GH docs is wrong!

[Deleted user]

But by removing the Resolve Issue permission, aren't we limiting the right to resolve issues to only a few team members?

[Jobin Kuruvilla [Adaptavist]]

Yes, but you can always have your own rules in the workflows. Just remove that condition from the Resolve workflow operation and add a new one! So that wouldn't be a blocker.

[Jobin Kuruvilla [Adaptavist]]

You can do it using the 'Resolve Issue' permission.

http://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions