Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. AUTO-929

More specific insights and controls to help admins manage automation usage and performance

XMLWordPrintable

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

    • Jira Software, Jira Service Management, Jira Work Management, Confluence

      Problem Definition

      The newly implemented automation calculation model counts the automation usage individually for each product.

      However, on the Performance Insights page, where the performance analysis and potential enhancements are conducted for automation rules, there is currently no capability to filter the information on a product-by-product basis.

      Suggested Solution

      Performance Insights page should be enhanced to provide detailed insights for each product separately allowing for a more granular analysis and understanding of performance metrics for individual products.

      Why this is important?

      The lack of filtering ability prevents us from effectively measuring the impact of improvements for each specific product. This limitation hinders the capacity to conduct comprehensive and specific performance evaluation and enhancement.

      Workaround 

      Currently, there is no workaround.

            [AUTO-929] More specific insights and controls to help admins manage automation usage and performance

            Tahir Kulelija added a comment -

            Implementing such a large change that will impact a lot of customers without giving those customers the granular visibility of the change is so counter productive and backwards. For some strange reason I had expected better.

             

            We really need to be able to see what is counted towards our quota and be better informed in order to implement the required changes.

            Tahir Kulelija added a comment - Implementing such a large change that will impact a lot of customers without giving those customers the granular visibility of the change is so counter productive and backwards. For some strange reason I had expected better.   We really need to be able to see what is counted towards our quota and be better informed in order to implement the required changes.

            Haddon Fisher added a comment -

            We definitely need this, and I'd add that we probably need quite a bit more around reporting here if we are going to continue to allow project admins to use Automation. Off the top of my head:

            • The current utilization chart and table break down numbers by month, making it impossible to effectively determine whether changes have an impact on utilization numbers. We should be able to filter this by arbitrary dates. This will always be needed, because people won't see spikes or bust their limits only on month boundaries.
            • Filters by project. We'll likely have to put in some soft per-project limits and also we will need to identify people who need Automation re-training.

            Haddon Fisher added a comment - We definitely need this, and I'd add that we probably need quite a bit more around reporting here if we are going to continue to allow project admins to use Automation. Off the top of my head: The current utilization chart and table break down numbers by month, making it impossible to effectively determine whether changes have an impact on utilization numbers. We should be able to filter this by arbitrary dates. This will always be needed, because people won't see spikes or bust their limits only on month boundaries. Filters by project. We'll likely have to put in some soft per-project limits and also we will need to identify people who need Automation re-training.

              e0eb84d6fb47 Dhanapal Mohanasamy
              2711b2aa3c24 Barışcan Elkama
              Votes:
              14 Vote for this issue
              Watchers:
              17 Start watching this issue

                Created:
                Updated: