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

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      In JIRA, the Average Time in Status gadget only report on issues closed in the past 24 hours. This is a suggestion to allow the time of the gadget to be extended.

      For example, instead of 24 hours, we could use days/weeks, so we would be able to retrieve more content for the report.

            [JRACLOUD-62999] Extend Average Time for Time in Status Gadget

            Atlassian Update - January 2024

            Hi everyone,

            Thank you for bringing this suggestion to our attention.

            As explained in our new features 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!

            Anusha Rutnam added a comment - Atlassian Update - January 2024 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new features 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!

            We have a project that may have 1 or less tasks completed in a given day as the task involves a long workflow that may take months as it passes between different groups. I would like to be able to see the time in status across a full project or filter by specifying a date range that is longer than 24 hours - a range defined by me. By checking the average time in status on a monthly or quarterly basis we can see if our overall process is improving or declining. There is some rich data that is currently hidden by the lack of flexibility in reporting.

            Brian Lucas added a comment - We have a project that may have 1 or less tasks completed in a given day as the task involves a long workflow that may take months as it passes between different groups. I would like to be able to see the time in status across a full project or filter by specifying a date range that is longer than 24 hours - a range defined by me. By checking the average time in status on a monthly or quarterly basis we can see if our overall process is improving or declining. There is some rich data that is currently hidden by the lack of flexibility in reporting.

              Unassigned Unassigned
              gdecampos Giuliano C.
              Votes:
              7 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: