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

Automatically add dropdown value to the main field

Hi All,


I have one query.

So, we have two fields with same name, but field type is different.

Field name- Project name (Single choice and text box)


1. Project name (choice) have dropdowns like "Project 1", "Project 2", "Project 3" and "Other"

2. Project name- Text box.


When I select "Other" in the 1.Project name (Choice) and 2.Project name (text) should be populated in creating screen---- I achieved this with small behaviors.


Here, my challenge is When I type new value in 2.Project name (text) field, it must be automatically added in the 1.Project name (choice) field as a drop down, it should be visible next time while creating ticket along with my previous options.


Is this possible? Any automation available? Someone please guide me how to achieve this one.

Thanks in advance.




1 comment

Radek Dostál
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Apr 21, 2023 this might get you started

Jira has no thing for this so this does need to be scripted. Ideally as a post-function because you wouldn't want to populate the list during the create, since the user could enter a tons of weird strings before they finally submit the issue.

I don't really like the code there too much (a bit bare bones?) and I think that it should be

// instead of companyField.getRelevantConfig(IssueContext.GLOBAL)

since you're guaranteed to get the correct FieldConfig and not just rely on "global" being the right fit, but oh well, it's verified


Log in or Sign up to comment