Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-22403

Ability to define multiple global contexts for custom fields

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • 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.

      I want to be able to create a custom field that is used for 2 different issue types – say Bug & Improvement. For Bug issues, I want the options to be A,B,C,D. For Improvement, I want the options to be A,B,D,E,F.

      JIRA only allows me to define 1 global context – not having to select specific projects – for the custom field. So if I set up a context for Bug issues w/ options A/B/C/D regardless of project, if I want to then define the context for Improvement issues with its separate options, I'm forced to explicitly select one or more projects to apply this to – even though I want it to apply to Improvement issues in all projects.

      This is a serious maintenance problem. As soon as I add more projects, I now have to remember to go back to my custom field and add those projects to the Improvement issue context. That's ridiculous.

      Is there a workaround for this?

      If you made Project Categories a 1st class, usable object in JIRA, at the very least you could allow us to define a separate context by Project category which would then automatically apply to all future Projects in that Category without having to explicitly add each & every Project into the Custom Field context as new ones are created.

              Unassigned Unassigned
              14bc6f9bf9fb David Goldstein
              Votes:
              35 Vote for this issue
              Watchers:
              29 Start watching this issue

                Created:
                Updated:
                Resolved: