I have a workflow that denies editing after reaching a particular status (this is not the closed status), there are several subsequent statuses.
I use the workflow property jira.issue.editable=false for this status. But i do not want to block the whole issue for editing. It must be possible for users to add attachments and edit some fields of the issue even when it is editable=false.
Is there a way to solve this?
The whole point of edit=false is to stop editing. That's what it's for.
Either remove it, or create a transition from status that goes back to the same status, with conditions to control who can use it, and with a screen that only includes the fields you want to let them update.
how does this work?
It is not working this way for me:
The issue is still editable
jira.issue.editable.denied = true.
I also can't find "denied" in the docs
It seems to exist (https://jira.atlassian.com/browse/JRASERVER-66836)
but i cant find it anywhere.
Hi @Jens Kisters,
I found "denied" in the last comment of the https://jira.atlassian.com/browse/JRASERVER-32230:
The proper format is is:
<property>.denied = whatever
Please note that an issue becomes uneditable when it is in the status where you define the jira.issue.editable=false or jira.issue.editable.denied = denied. I use the second one. I'm not sure whether it does matter, but this property is the first in my list. It works for me the way the Edit button disappears from issue page in particular status.
Jira ver 7.2.9
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs