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

Next-gen project statuses appearing on "Time in status" gadget or "Sub-task blocking condition" causes confusion

    XMLWordPrintable

Details

    • 0
    • 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.

    Description

      Summary

      If a user has next-gen projects, they will see statuses from those in the following pages:

      • Gadgets that use the Statuses in the configuration - "Time in Status" and "Filter Counts", for example
      • "Sub-Task Blocking Condition"

      Steps to Reproduce

      For Sub-Task Blocking Condition:

      1. Create a next-gen project
      2. Edit a transition of a Workflow for a classic project
      3. Click on Conditions
      4. Click on Add condition
      5. Click on Sub-Task Blocking Condition
      6. Observe multiple of the same status (e.g., DONE)

      For Gadgets

      1. Go to System dashboard
      2. Click on Add gadget
      3. Add Average Time in Status, for example
      4. Observe repeated statuses in Statuses section

      Expected Results

      Only show one instance of the status.

      Actual Results

      Shows 1 + (the number of next-gen projects there are). For example, if an instance has 5 next-gen projects, it shows DONE 6 times.

      Workaround

      1. Change the name of the status on the Statuses page
      2. Perform the desired change
      3. Change the name of the status back to it's original value on the Statues page

      Attachments

        Issue Links

          Activity

            People

              jwong@atlassian.com Jason Wong
              mmarney@atlassian.com Matthew M. (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: