-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
User story suggestion
As an automation rule writer
I want a warning error message logged when the issue processing limit (100) is exceeded
So I have visibility that some issues were not processed by the automation rule
Acceptance criteria
- When a trigger gathers more than 100 issues, log the limit was exceeded and continue processing with the first 100 issues
- When a branch gathers more than 100 issues, log the limit was exceeded and continue processing with the first 100 issues
- Bonus: rule detail has a setting to halt the rule when more than 100 issues are encountered for processing. The default for this setting is disabled, preserving prior behavior.
Business case
As more customers rely upon automation rules, knowing which issues processed (or did not) is a key to success. Today, rules only process the first 100 issues gathered and there is limited visibility when the limit is exceeded. For JQL which can be resolved during development, this can be tested with Validate Query. However this validation is only confirmed at a point in time and does not help later. For branches of related issues, there is no such validation; thus exceeding the limit for links or sub-tasks is not visible.
- relates to
-
A4J-2683 Loading...