Navigating the Transition: Migrating Client Instances to Jira Field Schemes

[#1]

👋 Hello Solution Partners,

As we evolve Jira’s field configuration model, we want to ensure you have everything you need to guide your clients through the change. This guide outlines the shift from legacy Field Configurations to a unified Field Scheme architecture and will help you plan your clients' migration strategy.

What’s Changing for Your Clients?
The conceptual model is shifting to be more intuitive but requires a different approach to configuration:

• Simplified Architecture: The "Field Configuration" as a standalone container is being deprecated. It is replaced by Field Parameters defined directly within a Field Scheme.

• Work Type Overrides: Instead of mapping different configurations to different issue types, you now use Work Type Parameters to create overrides within a single scheme.

• Direct Project Association: Schemes are now associated with projects directly, making the relationship much clearer in the API.

Migration Best Practices:

1. Audit Field Visibility: Since isHidden is replaced by field association, review which fields are truly necessary for each project before migrating.

2. Leverage Bulk Operations: Use the new bulk endpoints to standardise field descriptions or requirements across multiple client projects simultaneously.

Detailed Migration Reference
To help you plan complex transitions for your clients, you can find the complete technical specification and endpoint mapping in the https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/From-Field-Configurations-to-Field-Schemes-Migration-Guide-for/ba-p/3245633