Uploaded image for project: 'Jira Cloud (including JIRA Core)'
  1. Jira Cloud (including JIRA Core)
  2. JRACLOUD-6851

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



    • UIS:
    • Support reference count:
    • Feedback Policy:

      Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.


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

      Atlassian Update – 4 January 2016

      Hi everyone,

      Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience. We have reviewed this issue over the last few days.

      Simplifying project setup, configuration, and maintenance is one of the JIRA team's top priorities right now. We are in the early stages of a big investment in making it easier to get started with a JIRA project and maintain a large number of projects at scale.

      We expect that our work will eventually incorporate additional flexibility for configuring field behavior on a per-project basis, but we can't make any commitments on exactly what we will support or when this will be released.

      We will continue to update this issue as we release new capabilities for project administration. Please don't hesitate to contact me if you have any questions or feedback.

      It's important to understand that we rarely try to implement individual features from jira.atlassian.com, but instead take a holistic look at the problem and use feedback from the comments here and a dozen other sources of customer input to solve the core problems.

      Please don't hesitate to contact me if you have any questions or feedback.

      Dave Meyer
      Product Manager, JIRA Platform

      In the custom field configuration context, it is not possible to choose a project if it has already been associated to another configuration context of the same custom field. For instance, it is not possible to make the following associations:

      Task, project1, configuration context 1
      Task, project2, configuration context 2
      Bug, project1, configuration context 3
      Bug, project2, configuration context 4


          Issue Links



              Unassigned Unassigned
              rickye Richard THIBAULT
              536 Vote for this issue
              305 Start watching this issue