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,554,892
Community Members
 
Community Events
184
Community Groups

Jira Automation fields drop down has values that doesn't exist

Why does the drop down in the Automation have two different Labels fields (on top of the System one)? We don't have such custom fields and if it was deleted, it's been more than 60 days. Don't understand where they are coming from. 

There are many many other fields that don't exist as well and it makes building automation very cumbersome because I don't know which ones are being used! 

 

Screenshot 2023-04-27 at 17.22.32.pngScreenshot 2023-04-27 at 17.23.07.pngScreenshot 2023-04-27 at 17.23.12.png

1 answer

1 accepted

0 votes
Answer accepted
Walter Buggenhout _ACA IT_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 27, 2023

Hi @krauch and welcome to the Community!

It is very likely that those fields that you don't find in the list of custom fields are either system fields (like the first Labels field in your screenshot) or fields from team managed projects. Those projects have their own, siloed configuration and those fields are not managed centrally in Jira. But you may want to automate those as well of course.

Hope this helps!

Ah I see, so these team managed custom fields would be configured in each individual team managed board... So if I wanted to clean up and get rid of these custom fields, I would have to find the team managed board that is using the custom field and switch that over to the system field and delete that custom field from the team managed board settings? 

There is no way to centrally see all the custom fields that team managed boards are using?

Suggest an answer

Log in or Sign up to answer