We’re improving Fields management in the Admin pages of Jira

[Carol Low]

@Rune Rasmussen - I've spoken to the community team, and there is an option to only get notified for major edits - the setting was a bit hard to find but it's here:

Hopefully this helps to reduce your notification noise!

[Carol Low]

@Yatish Madhav -

Thanks for your continual input (and everyone here really).

Yes, “Field Schemes” is what we envision as the simplified/merged state of field config and field config schemes. We’ve done concept testing and progressing to build, but there will be opportunities for early access here as we want to make sure it lands in good shape. I've got your email and will reach out when we are ready.

@Kelly Arrey -

Thanks for sharing your example - indeed the upcoming changes are meant to address what you’ve shown.

At the end state, you’ll be able to see all the fields easier on the Fields page and manage them. Quick note though, that fields dropdown in your screenshot does “collapses” all the team-managed fields with the same name and type into 1, so in reality when you see your team-managed fields you may see multiples. This is also why we want to give you better visibility so you can choose to use a single, global field instead.

@Josh - 

noted on what you need for actions - sounds really reasonable to me.

@Stefan Draber -

Hi Stefan, if the cosmic power granted me the ability to magically add sorting and filtering columns at one go, it’ll be the first thing I do.

Without making it an excuse, the reality is that some of the admin pages are so old and still on legacy code stacks they aren’t taking advantage of our design system and so every change takes a long time.

Keep your voices coming and the pressure on us to keep propagating these changes to all the pages.

@Rodolfo Romero - Adaptavist -

We’ll have to assess the impact to JCMA for each change and will update the documentation accordingly, for now, being aware of the potential concept changes and there will be some differences to “field contexts, field config, field config schemes” where at the end state the migrations won’t be a “lift and shift” is a good start. The end result should be better for the end-users with less clutter, and for admins a simplified mental model - but we recognise it is still a change and may be good to set expectations early on.

We’ll also be publishing any upcoming changes to APIs or new APIs in developer community, so developers can assess if they need to also make changes on their side.

Sorry I may have drifted from your original question at the end, but yes we are working with the JCMA teams and will keep impact to migrations minimal.

[Christian Calkins]

@Carol Low Thank you for posting this and answering so many questions in the comments.

I am looking forward to these upcoming changes! The custom field bloat is a looming project for me to deal with and these improvements will help me a lot!