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.
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.
There still old UI on some steps, which leads to unnecessary extra actions or misleading UI controls. People who used to work with previous UIs can handle this, newcomers will definitely struggle to fine-tune their fields.
to edit simple field options you have to click through 3 UI generations
I would love an export of all of the custom field information so we can do routine cleanup and align on the fields we are using. This is very helpful when merging Jira instances.
Are the adjustments to the custom fields and workflow editor a sign that leads towards being able to do proper configuration management through IaC-tools such as Terraform?
Atlassian Team members are employees working across the company in a wide variety of roles.
October 9, 2025 edited
Hey all,
Things have been busy on my end so this response is delayed - sorry for any inconvenience.
First some general responses:
To everyone asking for an export - we hear you loud and clear, please know that I have taken note of it, every comment helps us!
Field merging/consolidation/clean-up/prevention - we also hear you! We have changes in our backlog planned to ease this pain. Just to be transparent though, merging is complex given all the places fields are used, especially if they are being referenced through APIs and Apps outside of our visibility.
@Piotr Smialek - support for these field types are now available. Not all features go through Jira labs and this wasn't considered a beta release, but I understand that the ability to find the field types was not ideal and it would have helped (in hindsight).
@s.weber - are you on the new experience now? Are you on bundled release tracks by any chance?
@Haddon Fisher - appreciate the spicy take and I understand about smaller screens. From our analytics it showed most people use large screens in admin (but that could easily be because otherwise it would all be crammed) - we're actively exploring the best way to handle field editing for complex field types, where a side panel would be limiting.
@Bryan Morenc - Unfortunately that's not part of this initiative - hopefully support comes soon!
@Alexey - Simple field options editing is something we are working on soon. Thank you for your patience, we didn't want to wait until everything was done to share the goodness, but it does mean some parts are still legacy experiences.
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.
@Carol Low unlike some of the other recent UI changes, these improvements are going 100% in the right direction and are addressing long-standing pain points. Our team really appreciates the work you're doing here, so thank you!
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.
Thanks for the update Carol Low! After thinking about this a lot more (and doing a bunch of field work) and I think the real issue is less about the screen size itself and more the first issue "It doesn't feel like a scalable solution that can actually fit all of the controls, particularly for the more complex custom field types."
Some changes I can make in the rail and some require me to jump into a new tab - it feels much more disjointed than the old model of "new tab every time". This feels like it can't make up it's mind about what the UX should be and "split the middle" which just doesn't work. My 2 cents would be "it should only take us a single click to get where we need, and we should be able to do everything we need to from there".
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.
It would be great if we can have a mechanism to archive fields instead of just deleting them. Our company as a financial institution has a policy that no data may be deleted and data must be retained indefinitely. Because of this we are unable to delete custom fields that we no longer use even if the project has been archived.
It would be nice to have the mechanism to archive these fields so that they no longer appear in searches or anywhere else but at least the data captured against the field is still there if needed for audits.
I've ended up manipulating fields (often putting loads of text into the Description) in archive projects so I can remove outdated custom fields from searches - archiving the fields themselves would make life much cleaner and a better user experience
90 comments