When a developer picks up an issue to resolve the status changes to "In Progress" and the assignee is the developer. Whilst in this state is it possible to restrict issue update access to the asignee and administrators only ?
The reason for this request is primarily "scope creep". On occassion a developer will commence work on an issue only to find someone updates the issue, with best intentions, resulting in a change in the scope of what was originally required.
in "In Progress" status property, set jira.permission.edit.group.1=<some-group-name>
Yes. Check this out: http://www.j-tricks.com/1/post/2011/02/permissions-based-on-workflow-status.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the link, followed the guide notes and managed to achieve what was required. Brilliant !
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It doesn't seem to work for our JIRA - 6.x. I want to forbid issue edit if it's in "Final" state and set jira.permission.edit=denied, but still am allowed to edit the issue. Tried jira.permission.edit_issue=denied as well, no luck. Any ideas? Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is easier for Edit. Try this on the Step and not transition:
Key: jira.issue.editable
Value: false
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Doesnt work.
Tried both options and Im still able to edit the issue
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.