I have created a custom workflow, which is as follows (simplified):
Open --> Draft --> Review --> Approve --> Development --> Complete
Now after an issue has been put to review, it should not be editable (the actual content... summary, description, etc). I found a way to make so by adding following to each of the steps that should not allow editing:
The problem is that now I cannot assign the issue while in those steps.
I have tried different approach by using...
value: <some group>
... but it does not do anything for me for some reason
I learned that if I remove edit permission from project settings, I can't edit the content, but I can assign. That is exactly what I want, but I need to be able to change that per step.
Any ideas? All help is appreciated!
There was a similar request a couple years ago at JRASERVER-6381 that was closed as will not fix.
Take a look at the Communities post How to restrict Jira ticket description field edit permission. Scroll down towards the bottom and you'll see Nic's suggestion to do this.
Thanks for your help.
In the Community post that you linked there was this at the bottom:
"There is another trick, which is painful to set up and maintain - you can set workflow properties to control the groups which can or cannot edit an issue when it is in a certain state in the workflow. As issue types can be set to use different workflows, you'd need one workflow for each different edit scheme."
This is what I tried, but for some reason it doesn't do anything.
To be more precise...
1) I created 2 accounts. One of them belongs to group: jira-administrators
2) In my workflow I added: "jira.permission.edit.group=jira-administrators" to one of the steps
--> both were still able to edit the issues in the step
3) edited project permissions from project settings by removing the permission to edit from "any logged in user"
--> neither of the users were able to edit the issues in the step
To me it seemed like the "jira.permission.edit.group=jira-administrators" had no effect.
Statuspage customers logged more than 194 years of collective incidents in 2018. That’s a whopping 87% increase from the 104 years logged in 2017 , and we aren’t even through December yet....
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