nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Using jira.permission.edit.user in a workflow status properties

Athar Mushtaq_kpzf39

I am trying to lock user stories for a workflow and allow a specific user to still be able to edit it. I came across this documentation and I tried adding jira.permission.edit.user as the property key and value as a name of the user (Also tried using an ID) but it didn't work. It locks the requirement for that specific user as well.

Just wondering what value of a user should I add to allow him/her to be able to edit it.

Accepted answers

Andy Rusnak

Hi Athar,

Thanks for posting your question on the Atlassian Community!

As I understand the issue you are running into, you set the jira.issue.editable to false within your workflow but then want the ability to override that permission for a specific user. Thus giving that one user the permission to edit the issue using the jira.permission.edit.user property while not allowing anyone else to edit issues in that status.

I believe to solve this issue, you would want to use the jira.permision.edit.user without the jira.issue.editable permission in your Workflow. You just need to note the entity you would want to be able to edit the issues when in this status. This should restrict all others from modifying the issue. So for example, if I wanted just a single user with the username "andy" to be able to edit the issue when in this status, I would add the following property to the status:

Property Key: jira.permission.edit.user

Property Value: andy

This would only allow the user andy to be able to edit the issue when in this status.

The jira.issue.editable cannot be overridden by other properties. So if you set that permission that will limit everyone from editing the issue. There has been a request to add this functionality into Jira for a future release but the requests were closed due to a lack of interest from the Community

JIRASERVER-63580 -- Allow Other Workflow Properties Override jira.issue.editable=false

JIRACLOUD-63580 -- Allow Other Workflow Properties Override jira.issue.editable=false

Please let know if this solution mentioned above would work for you. If I have misunderstood your scenario or you have additional questions related to this I would be more than happy to discuss further as well.

Thanks,

Andy

All comments

Andy Rusnak

Hi Athar,

Thanks for posting your question on the Atlassian Community!

Property Key: jira.permission.edit.user

Property Value: andy

This would only allow the user andy to be able to edit the issue when in this status.

JIRASERVER-63580 -- Allow Other Workflow Properties Override jira.issue.editable=false

JIRACLOUD-63580 -- Allow Other Workflow Properties Override jira.issue.editable=false

Thanks,

Andy

Athar Mushtaq_kpzf39

Hey Andy,

Thanks for your reply and the suggestion. I have tried using this numerous times by using the Property Key = jira.permission.edit.user and Property Value: athar. This doesn't work for some reason. It locks me out of editing the particular issue type as well. Please note I am not using jira.issue.editable property for any status in the workflow.

Andy Rusnak

Hey Athar,

That's interesting that isn't working. If you remove that property are you able to edit the issue again?

Can you also confirm there are no spaces or anything in the property value? It has to match the username exactly as it is shown in User Management. If it is locking your access to the issue through this property, I suspect the property key is working as we want, but the property value isn't matching somehow. So we might just need to run down what is causing that behavior.

Best,

Andy

Athar Mushtaq_kpzf39

Hey Andy,

I didn't have an access to user management and tried using my first name, surname, fullname and ID to make it work. Just found my username through activity feed which is a 30ish long character (Maybe a username was never setup). It worked and the issue was open for me to edit and no one else could edit it.

Thank you for your help on this

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud