-
Suggestion
-
Resolution: Duplicate
-
-
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.
- duplicates
-
AUTO-1007 More flexible/Separate billing options for Automation limits, e.g. ability to purchase automation runs as an add-on, ability to pool limits across products, minimum allowance for Premium customers with <5 users
- Gathering Interest