Carol Low Atlassian Team

Hi all - apologies for the delay in response, I had taken some personal leave + the community migration has let this slip off my radar. For every site on Continuous Release Tracks, this has now been fully released. If your site is still on legacy schemes, this is likely the site is on Bundled Release Tracks. Its already…

@Vitalii Zapolskyi - this is still there, perhaps a bit harder to find! You can find this in the actions menu on the Field schemes page. @Tere Pile - It would depend on how you have been using using field contexts - if you mostly use global field contexts, it shouldn't result in individual schemes, but if you use them…

@Dirk Ronsmans @Brita Moorus @Dusty Brossart - great to hear! @Lior Pinelis - it would work for JSM but no plan to support Request Types as yet. @Paul Pasler _Seibert_ - please feel free to direct these questions to the team in your request ticket, some of these are better answered by the eng team. Exclusions from the EAP…

@Rodolfo Romero - Adaptavist @David Yu @Rupa Goyal - DC to cloud migrations will convert field config and field config schemes if the target site has new field schemes enabled. For Cloud to Cloud migrations - there will be a warning if your source and destination sites have different enablement statuses, and you will be…

@BG Pantaleon - There is no action you need to take before or after. End users will have their views preserved. Some admins are taking this as an opportunity to perform a clean up, especially if they are close to the field limits…

@Nicole Shepherd - This is possible for sites that heavily relied on field contexts to manage visibility (and we get it, it was very convoluted with field configurations and field configuration schemes). We've shifting where this management sits, so you should have to worry about field contexts less from now on. Before…

hi @Andrew Culver - I can see you signed up on the EAP using your sandbox, and a different person signed up for your production site. We had offered different migration options during the EAP, so it's possible it was due to the other option being applied to your production site. Can you please let us know which site you…

@Juan Carlos Pin - I had a quick browse and didn't see the recording on the on demand library yet - I'll update you if it becomes available! @Susanne Harelius I hear you - we are conscious that previously a lot of schemes are kept the same, but recently with the introduction of limits in fields, we think the trade-off to…

@__ Jimi Wikman We handle the move of data to maintain visibility in our migration - yes this may mean a lot of schemes are created - if you join the Open Beta using a sandbox, you will be able to see exactly how many new schemes will actually be created. We have a lot of customers in early access with a lot of contexts…

@Michael Brändel Thanks for your feedback! You can filter for only company-managed fields in this filter: For adding fields to screen, while we aren't working on that, I find a way around it is to go to the Field, and use the action menu to "Add field to Screen", if you have the screen names handy. Finally, we have looked…

@Marini Simone - it still works! Please go to the "Fields" section in Space settings to find global fields. 

@Mathew Lederman - not directly as a part of this change, but the foundational work done means we are able to get started on it in parallel. I'm preparing for some prototype testing soon.

@mruttan - no need to, your spaces will work as they do today.

Hi everyone, I've now curated the FAQs into this new post, which also provides an updated rollout timing of May/June instead of the initial target of April. Please have a read and I hope this helps to clarify the new Field Schemes more. Regards, Carol

@Brian R @Stefan Draber @Josh - We haven't given much thought to aliases. Thank you for the insights, I will have a look into this. I know for request forms there is a way to do this already (and assumed so for advanced forms too) but that is more only for the customer portal and the field name is still consistent within…

@Hugo Navia - Thanks for this suggestion and sharing how you are doing it right now. We'll see what we can do here. @orla_mears - Visual demos is definitely on the books - however during Open Beta we are still evolving some UI elements (and taking onboard feedback), so this will be ready closer to GA. @Sascha Weber - Thank…

Happy new year everyone! @Kasturee & @Debbie Jolley - noted about archiving fields. I can see how it can help with instance cleanliness. It's not currently on our plans, but I've captured this. thank you. @David Laine - the fields permanently delete automatically after 60 days. In that time, the field behaves exactly like…

To everyone, Thank you for your engagement over the year, I truly appreciate all the feedback and passion from you all - it makes my work fun and worth it. I'm taking some time over the end of year now, so wishing you all Happy Holidays and see you in the 2026! Cheers, Carol

@Shai Gilboa - you have understood it beautifully. "If a field has no 'default' context associated with 'all spaces' context, but only context associated with specific spaces (doesn't matter if all work types of specific ones), and a space has this field associated via Field Scheme, what will happen? Will the screen appear…

@Joao Zampa - thank you for your suggestion - this is definitely something we are considering for the future, with the right level of permissions.

@Andrew Culver - You'll be able to do this through grouping the projects into Field schemes and only adding those fields into the Field scheme. Since Field schemes will be more straightforward to manage than Field config and Field config schemes, it should be easier to manage relationships like this even without limiting…

@JG Meillaud _ - It's not in my screenshot, but you will be able to adjust the availability, required/optional, custom description for different work types as you did before. We are still testing out the UI, if you join the Beta you'll be able to try this out for yourself. We are planning to maintain all existing…

@Julia Foden - You are right, I did misunderstand, thank you for repeating and clarifying it for me. Your use case is still maintained and possible - there is no change here.

@Dave Mathijs - Field contexts will remain, they will only set values on fields. @Alex Koxaras -Relational- - Would I be able to convince you to give it a try and tell us what you don't like about it? Your feedback will be valuable. @chihara - sorry but https://jira.atlassian.com/browse/JRACLOUD-95298 will not be addressed…

@Rune Rasmussen - thanks for the link! I've fixed it up in my comment (I didn't notice I had added a space at the end, causing it to error). 

Hey everyone! We're currently collecting some data on how you utilise Field Contexts - if you have some time can you please fill out this survey - https://surveys.atlassian.com/jfe/form/SV_1NBr1k2W0GIAoUS The more details we can get from you the better! Thank you for your time in advance!

@Steve Rhodes - Yes this is the "All spaces" option in the dropdown, as only company-managed fields can be used in all spaces. We call them company-managed field colloquially but we want to be clear about what it means (where it can be used). @Eugene Victorov - Projects are being renamed to Spaces. It's still rolling out…

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…

Some general updates: 1) Searching by field IDs is progressively rolling out now. 2) You can now search for screens within the "screens" panel. For everyone I haven't mentioned, or replied to a specific suggestion, I've added them to my list of suggestions/feedback and we will review them holistically as we continue to…

Hey everyone, I've just posted an update which you can read here. @Carolyn Hinkel - great feedback, all duly noted for internal review. We have removed numbered pagination for the page as it is more performant, instead as you have described, it continues to load more fields. Is there a particular use case that numbered…