Hi,
we're using JIRA 7.8.1. and currently I'm struggling with field security. I set-up on every workflow status property 'jira.issue.editable' = 'false' in order to restrict edit permission for more users. Users can change the field values in transition.
However I'm not able to add attachment or create sub-task while status is not editable....could you please advise some workaround?
Thanks!
Petra
We have the same issue when we want to lock a ticket for edit changes at a specific status. At that point we are no longer able to add links are sub-tasks. I can understand the sub-tasks, but links are critical for plugins like Xray.
Yes. We have also observed the same issue. When we add 'jira.issue.editable' = 'false' property, attachment, Assign , Create sub-task operations are getting disappeared.
We are not able add the attachment by transition also ('jira.issue.editable' = 'false' is in the destination status). But we can change assignee using transition.
Alternatively you can use below property.
key: jira.permission.edit.group
value: none (or just another text - not matching any group).
Refer below link for more details.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Petra,
Edit permission is not the same as add attachment permission or add comment permission. Check your permission scheme.
Also, why don't you have your permission scheme with the edit permission empty instead of using that property in every status?
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.