You need to take a look at your permission scheme - the users need to have "resolve issue" permission. And it needs to be on screens.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Nic: Can user have permission to resolve the tickets but no permission to update FixVersion.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not in JIRA Core, but Software separates the permissions out when using boards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can anyone elaborate ? I found the following link which isn't that helpful - according to this, adding an issue to a version now requires Edit Issues Permission, which is again, a pretty global permission with overloaded semantics.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, that's wrong. "Edit issues" is a specific line in the permission scheme. It's certainly not a global permission, and there's no overloaded semantics, it's a single clear line.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Nic. Can you point to some documentation which explains how JIRA Software separates the permissions for resolving issues and the permissions for updating fixVersion when using boards ? The following link suggests that nothing has changed with respect to Resolve Issues Permission - https://confluence.atlassian.com/adminjiraserver072/managing-project-permissions-828787763.html Thanks again,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Will be happy if you can share how you solved it.
Thanks , Ofira
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There's already a "Schedule Issues" permission, which controls the ability to edit the "due date" field. Assigning a "fix version" to an issue is also scheduling the issue, so it would make sense for this to be controlled by the same permission.
It would also make sense if the default for an Agile project was for the Product Owner role to have this permission and not the developers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There are several option for:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.