Example: When an issue is moved to the 'backlog' status, I want to prevent the description field from being edited ever again, regardless of its new status, by a particular role (such as a client).
You can use the
jira.issue.editable flag to enable/disable editing of issues.
You can refer to this link: https://confluence.atlassian.com/display/JIRA/Allow+editing+of+Closed+Issues as a guideline
If you use Hashimis solution you could add to this Backlog status a transition called "Edit" which goes back to Backlog. Add a screen to this transition with all but description field. So for a user it looks like the Edit button has moved and the user won't be able to edit the description when he clicks the "Edit" transition.
The Live Fields feature from JJupin plugin can disable a field(i.e. make it read-only). Check it out: http://confluence.kepler-rominfo.com/display/JJUP30/lfDisable , we have a couple of tutorials and recipes here too: http://confluence.kepler-rominfo.com/display/TR/Tutorials . All of them are powered by our Simple Issue Language (SIL).
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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