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

Allow unused execution rules on a product to be used if all other product limits are reached

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

      Currently, if a plan hits their monthly execution limits for say, JSW, but they still have excess amounts of exeuctions left over for another product like JWM or JSM, any rules running under JSW will still continue to fail because the limit for that specific product has been reached.

      It would be a nice QoL change to allow some of the JSM execution limits to be used in place when the limit of the others have been reached. Uses shouldn't be able to use any limits not meant for the correct product initially, but only in cases of when the main product limit has been breached already and a bit more is needed to make it to the next reset. This would avoid a lot of headache for the user and avoid the need to upgrade to a higher tier for just a few more executions per month.

              Unassigned Unassigned
              3176abc1c383 Hieuy Mac
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: