Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


What is the method to lock edit access of description in JIRA tickets after updating?

Harshada Nagare
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Oct 27, 2023

I am looking for the way where once ticket is updated should not be edited by other team members. Similar to google sheet where we protect our data and keep as Read only.

1 answer

1 accepted

0 votes
Answer accepted
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 28, 2023

Welcome to the Atlassian Community!

I am sorry that the answer you got before was misleading - it was generated by an AI that has no understanding of your question or Atlassian software.

There are a couple of ways to do this, but you need to think carefully about the conditions under which you want to do it, because there is no "lock" for a field.

The easy one is to remove the field from the "edit" screen - this makes the field uneditable for everyone.  If you want to still be able to edit the field, then you will have to add transitions to the workflow with screens that include the description field, and then use conditions on those transitions to limit them to users, groups, roles, reporter, assignee, etc.

The harder one to implement is to add workflow properties to your workflow that can lock down the ability to edit the issue at certain status in the workflow, again narrowing the rights down to certain people, but this affects ALL fields, not just description.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events