Allow more than one custom field context to be associated with the same project but different issue types

NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

Hi everyone,

As always, thank you for watching, commenting and engaging with us on this ticket. As you might be aware, we’ve gone through a recent re-balancing exercise here at Atlassian to better reflect operating in a changing and difficult macroeconomic environment. As part of the difficult decisions that have been made to prioritise the most critical work for our customers, we’ve had to put this work on pause for the next few quarters.

In terms of silver linings, I’d like to share that we have made progress on investigating and clarifying the requirements and engineering work that is required, so when we are ready to pick this up again, we won't have to go back to zero.

I know that this is disappointing for many of you, especially in light of the previous update, please accept my sincere thanks for your patience and understanding for this matter.

Regards

Carol

—

Update from November 2022

Hi everyone,

Thank you for watching, voting, and commenting on this issue. We hear you that it is important to have more control over configuring your fields across different issue types in the same project. We are in the middle of a larger initiative to improve the way fields can be configured, and will be picking up this feature request early next year. We have started design work for this and will be onboarding a team to work on it from Q1 next year, and I will provide periodical updates on this ticket.

While we’re building this and other improvements to how you configure fields in Jira, we welcome you to join our focus group and work with us to shape the future of configuration in Jira. If you are interested, please email me at clow@atlassian.com and I’ll share more details on the group.

Regards

Carol & the Atlassian team