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

Average Time In Status - Cycle Time Calculations

XMLWordPrintable

    • 2

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

      Hi Atlassian Support Team,

       

      The company I work with needs to calculate cycle time spent in any given workflow status for each epic, issue, and sub-task in our Jira Projects.  I currently use your, "Average Time in Status," gadget on a dashboard for metrics however, the average can very easily be altered by an outlier that cannot currently be filtered out.

      For any given epic, issue, and sub-task, we need to be able to see (perhaps in a custom field) and export:

      1. The date the epic/issue/subtask is moved into the status, "In Progress," (or any status for that matter).
      2. The date the epic/issue/subtask is resolved or closed.

      These features do not necessarily need to be in a gadget but I do need the ability to view and export the above information.

       

       

      Please contact Katrina Lieber for specific case usage at 970-407-6259 or  katrina.lieber@aei.com

       

            [JRACLOUD-73399] Average Time In Status - Cycle Time Calculations

            Matthew Hunter added a comment -
            Atlassian Update - April 21, 2023

            Hi everyone,

            Thank you for bringing this suggestion to our attention.

            As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team!

            Matthew Hunter added a comment - Atlassian Update - April 21, 2023 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team!

              Unassigned Unassigned
              227964843e79 Katrina.Lieber
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: