Degraded performance Customers may experience intermittent errors using Community search. Our platform vendor is investigating.
Possibly, depending on when you want this "lock" to occur.
You can remove the field from the "edit" screen, but that removes any ability change the field in general - your users will only be able to change it during transitions.
Editing (and creating) comments is unrelated to screens (have a look at the permission scheme for the progect), and the ability to change status is controlled by conditions on your workflow.
JIRA doesn't have field level permissions per se. The only way I know of protecting a field from editing is to leave it off the edit screen. Then, you would create loopback transitions to each status (a transition that ends in the same status). On that transition, you could set your permission condition and expose the field on that transition screen.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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