You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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!
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.