Issue Summary

      There are some issue statuses: (Waiting for support) & (Waiting for customer) that auto-generated by Jira Service Desk are categorized with a "No Category". The "No Category" is not allowed in normal Jira usage where all statues are required to be categorized into:

      • To Do
      • In Progress
      • Done

      Steps to Reproduce

      1. Install Jira Service Desk.
      2. Create a Service Desk project.
      3. Check the workflow(for Service or Service Request type).

      Expected Results

      Service Desk creates the workflow with all the status in a valid category, "To Do", "In Progress" or "Done".

      Actual Results

      Service Desk creates two status, "Waiting for support" and "Waiting for customer" without a category, they are set to "No Category" with the grey color.

      Notes

      Normally when you create a status you cannot choose "No Category".
      Having a status with no category can affect the Kanban board with the "Hide Completed issues" feature. Issues on a status without a category will be removed from the board as well as done issues.

      Workaround

      You can change the category of the status after it has been created.

          Form Name

            [JSDSERVER-6355] Service Desk workflow creates status without category

            Because Statuses are global to Jira if you correct the status category once all new projects will have the correct category.

            Lachlan G (Inactive) added a comment - Because Statuses are global to Jira if you correct the status category once all new projects will have the correct category.

            mkaras hi, it looks like this bug belongs to JSD which begs the question: which version of service desk should we pick for this? The latest one? JSD doesn't follow the same version path as server. Cheers.

            Mateusz Walas (Inactive) added a comment - mkaras hi, it looks like this bug belongs to JSD which begs the question: which version of service desk should we pick for this? The latest one? JSD doesn't follow the same version path as server. Cheers.

              lgoodhewcook Lachlan G (Inactive)
              mkaras Mauricio Karas (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: