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.
When status has jira.issue.editable=false property, self transition works for changing standard and custom fields, but does not work for adding Attachment. Attachment does not appear in an issue after pressing transition button.
Jira ver 7.2.9
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In case set jira.issue.editable.denied = denied, jira issue is not editable, but Attach files button is visible and works well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Alexey,
how does this work?
It is not working this way for me:
The issue is still editable
Also tried
jira.issue.editable=denied
jira.issue.editable.denied = true.
I also can't find "denied" in the docs
https://confluence.atlassian.com/adminjiraserver079/workflow-properties-950288814.html
It seems to exist (https://jira.atlassian.com/browse/JRASERVER-66836)
but i cant find it anywhere.
Cheers
Jens
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Jens Kisters __SeibertSolutions,
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.