We're using a modified version of the Change workflow and we'd like to be able to restrict the Change Issues to read-only after they have passed the approval process. I tried searching on this topic and found some references to setting status/transition properties but nothing I've tried so far has worked.
Properties attempts thus far:
Key: jira.issue.editable Value: False
Key: sd.issue.editable Value: False
Key: servicedesk.issue.editable Value: False
It doesn't make sense to me to allow the details of a Change to be modified after it has acquired all necessary approvals so this is a pretty big obstacle for us. Any help would be greatly appreciated!
I was able to find the solution to this problem. Turns out I was very close from the beginning but the Value field is case-sensitive. I was using "False" but it has to be "false".
So in order to make an issue non-editable during a specific status then you'll need to add the following property to the workflow status:
Property Key: jira.issue.editable and the Property Value: false
Didn't notice the linked video at first. I just watched it but the problem I have isn't related to a transition. The solution I'm trying to find is to make all Change requests read-only to everyone after it has been approved. Right now I am able to edit all of the fields from the Agent view even after the request is Closed. That would create a major audit risk for us.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hi, everyone! Molly here from the Jira Service Desk Product Marketing Team :). In the spirit of this month's august-challenge, we're sourcing stories of Jira Service Desk activation fro...
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