We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
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.

    • 3
    • 9
    • 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 Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.

      Multiple Issue Type for Customer Request Type (CRT).

      With this feature one can change the Issue Type without clearing Customer Request Type. This makes recategorization of a Ticket viable and easy in for example a workflow transition. A Request for IT Help could be both an Incident and Service Request.

      As a Service Desk Agent I want to easily change the Issue Type while keeping Customer Request Type so that I can still see how the Ticket was submitted so that I can later Report on total "Requests for Help" and distuingish on how many are actually Incidents or Service Requests.

      As it is today when you change Issue Type CRT is cleared. Workaround is to either create a custom field "ITIL Classification" or create multiple CRT with different Issue Type, but then Customer has to decide whether said issue is Request or Incident.

      A workaround Suggestion is Sub Issue Types for JIRA Project.

            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.

              • 3
              • 9
              • 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 Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.

                Multiple Issue Type for Customer Request Type (CRT).

                With this feature one can change the Issue Type without clearing Customer Request Type. This makes recategorization of a Ticket viable and easy in for example a workflow transition. A Request for IT Help could be both an Incident and Service Request.

                As a Service Desk Agent I want to easily change the Issue Type while keeping Customer Request Type so that I can still see how the Ticket was submitted so that I can later Report on total "Requests for Help" and distuingish on how many are actually Incidents or Service Requests.

                As it is today when you change Issue Type CRT is cleared. Workaround is to either create a custom field "ITIL Classification" or create multiple CRT with different Issue Type, but then Customer has to decide whether said issue is Request or Incident.

                A workaround Suggestion is Sub Issue Types for JIRA Project.

                        a620038e6229 Jehan Gonsalkorale
                        50f3a3a792e4 Alf Karlsen
                        Votes:
                        57 Vote for this issue
                        Watchers:
                        41 Start watching this issue

                          Created:
                          Updated:

                            a620038e6229 Jehan Gonsalkorale
                            50f3a3a792e4 Alf Karlsen
                            Votes:
                            57 Vote for this issue
                            Watchers:
                            41 Start watching this issue

                              Created:
                              Updated: