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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,556,709
Community Members
 
Community Events
184
Community Groups

How to make a custom field readonly or disabled in Jira Automation action

I have a custom field with two values: Yes and No. Default is "No".

I would like to create an automation rule as follows:

When the value of the field changes to "Yes" then:

  •  send and email
  •  make the field non-editable or readonly, so that the field value cannot be changed again.

The first action is easy. But I am not able to figure out how to prevent the field from being modified again. None of the currently available options for a new action seem to do this.

Any help would be appreciated. 

 

Thanks,

Shiv.

 

 

1 answer

Is this in a company managed project? You might try removing the field from the Edit screen, and instead only allow it to be changed from a Workflow Transition that loops back to the current status. Something like a transition "Set X to Yes" that sets the field, and then you would be able to add a Condition to that transition to only display that when that field value is not "Yes".

It is a company managed project. 

Thanks. Your workaround makes sense. However, it will be great to have a simpler solution (if there is one). 

I would be stoked for something simpler too! Unfortunately, individual field security/permissions has been a long running request. IIRC there are a few third party apps in the marketplace that help, but otherwise we are left to control it through the transitions/screens. Please update your issue here if you happen to find something easier.

Will do. Thanks David. 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events