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!


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
Community Members
Community Events
Community Groups

Update estimation field according to issue type

Hi all,

I'm trying to find a way that t-shirt estimation field dropdown values will be based on selected issue type:

epic - S, M, L

initiative - XL, XXL

Until today both epics or initiatives used all 5 options so I already have data in Jira that I don't want to affect (will remain the same until someone will try to update).


I've found a way (not sure if that's the correct one) with scrip runner to disable filed option.

As far as I understand, disable mean you don't see option but older data isn't affected. 

I'm trying to figure out what the script should look like and how can I make sure it will run on any case of create or update scenarios.

Once I've a script, should it run as behavior? Automation rule?


Thanks in advance,




2 answers

Trying again to see if someone knows how to solve this issue.

Thanks in advance.

0 votes
Mohamed Benziane
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jul 26, 2022


You can achieve this with a behaviour then bzsed on the issuetype your user will have different option for the field

Thanks @Mohamed Benziane for your answer.

I've set a behavior mapped to Epic and Initiative and put the script on the initializer. Is that the correct place)?

It seems that when trying to update existing issue it's changing the options but when create new Epic or Initiative, values aren't set. Also if I'm changing the issue type on the create screen from epic to initiative or vice versa, it doesn't change the options. 


Any idea how to solve this?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events