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

Improve Automation concurrency - request for expanding resources in automation, give visibility of how many number of concurrent executions are available in Automation, support monitoring of Automation queue

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.

      Summary Issue

      Many automation queues become "progress status", if many queues are running at the same time.
      It takes a long time to complete many queues.

      Problem

      If you created many Automation rules and run them in a short time, it would take a while for all automation events to execute.

      In Automation Audit log, many queue show under in progress, we can not distinguish which is "in progress" or "waiting".

      Suggestions
      • The customer requests expanding resources for Jira Automation.
      • It is not possible to monitor/predict how long will take to execute Automation events when there are too many to be executed. It is helpful if automation monitor shows the execution of the automation events queue to help to predict how long it can still take.
      • Currently, there's no way to produce an even load on the system when running multiple scheduled automation rules; this can cause performance issues in instances with heavy use of scheduled automation rules, with large spikes on common scheduled times (e.g. 9 a.m.). This also creates a challenge to scale operations effectively. Add a CRON expression that produces an even load on the system, running in an "interval"; for example, instead of running all automations precisely at 9 a.m., they would have an interval, 9 a.m. to 10 a.m., and would run evenly between this period, avoiding performance impacts. 

      Related suggestions

      • Visibility around scheduled rule execution times running at a best attempt basis - 
        • Currently our scheduled rule times run on a best attempt basis given the asynchronous nature of our queue along with other factors such as having a number of other rules queued to execute, the priority of scheduled execution vs events, large JQL search being used, and scheduling mechanism working in a best attempt fashion.

      This is not make clear in our UI or docs, it's presented as running at the exact time which can create a false impression that run times are time critical when it's unlikely it will run on the dot at the given time.

      As part of this we should also look to establish generally acceptable scheduled rule times, since currently it's not clear.

              e0eb84d6fb47 Dhanapal Mohanasamy (Inactive)
              38f0fdb790c2 K. Ariga
              Votes:
              21 Vote for this issue
              Watchers:
              20 Start watching this issue

                Created:
                Updated: