IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

    • 1
    • 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've been playing with the 'new' (to me) custom fields feature. Very cool. Especially how you can scope them to 'global, per project or per issue type'.

      We can also customize issue types, priorities and resolutions.

      I was wondering if it's crazy to dream of a day when JIRA might allow 'scoping' of these built-in fields as well?

      It would be very handy. We could open up our JIRA install to serve external customers that only wanted to have one issue type (IE: a complaint!)

      I think with many end-customers, having to select amongst bug, task, inprovement, new feature is daunting.

      And hey... while we're at it... the fields that appear on "the next page" like version, environment, assigned to, etc... Could those be configurable as well

      Does it sound like I'm wanting JIRA to morph into a CRM-like application?

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

              • 1
              • 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've been playing with the 'new' (to me) custom fields feature. Very cool. Especially how you can scope them to 'global, per project or per issue type'.

                We can also customize issue types, priorities and resolutions.

                I was wondering if it's crazy to dream of a day when JIRA might allow 'scoping' of these built-in fields as well?

                It would be very handy. We could open up our JIRA install to serve external customers that only wanted to have one issue type (IE: a complaint!)

                I think with many end-customers, having to select amongst bug, task, inprovement, new feature is daunting.

                And hey... while we're at it... the fields that appear on "the next page" like version, environment, assigned to, etc... Could those be configurable as well

                Does it sound like I'm wanting JIRA to morph into a CRM-like application?

                        Unassigned Unassigned
                        3fc3260fc0fb Mike Curwen
                        Votes:
                        33 Vote for this issue
                        Watchers:
                        12 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            3fc3260fc0fb Mike Curwen
                            Votes:
                            33 Vote for this issue
                            Watchers:
                            12 Start watching this issue

                              Created:
                              Updated:
                              Resolved: