Automation throttle

[Dave Symonds]

Go an automation that checks for a status = backlog and its being throttled - 1000 tickets - but the majority are resolved.  Is there a way to set a condition that will limit the search down to board specific tickets so it wont ever hit this limit?

[Aaron Brady]

Hello Dave, 

Setting the right conditions can help narrow down the results of the automation. You can do this a few ways. First, you can limit the automation to a single project. 

Second, you can use JQL to filter the results down to just the issues found withing the board/s that you want to use. Linked below is to an earlier question related to using JQL to return board specific results.

https://community.atlassian.com/t5/Jira-questions/JQL-to-list-all-issues-in-specific-quot-kanban-board-quot-or/qaq-p/1247706?utm_source=dm&utm_medium=unpaid-social&utm_campaign=P:online*O:community*I:social_share* 

Good Luck!

Aaron

[Trudy Claspill]

Adding to this to address a specific part of @Dave Symonds 's question, there is no JQL option to filter issues based on Boards. Boards themselves are based on Filters and an issue can be within scope for any number of filters and therefore within scope of multiple boards.

If you want to constrain the automation to the issues within a particular board, in addition to what @Aaron Brady said about setting the Automation to be for a specific project, you can also enhance the JQL to include the filter used by the board.

It would help us address your question more specifically if you showed us the details of your Automation Rule.

[Dave Symonds]

Thanks All - its only filtering on the board - there just happen to be > 1000 issues in the boards history.  When I set the first condition - this automation runs every two days - to check if status = backlog - it runs through every issue that has existed on the board so blows the 1000 limit. 

I am after a way to avoid this - would archive work or is there some clever way to filter down without running through the entire issue list.

I am setting a reminder email for anything still in backlog over two days that hasnt been acted on

Thanks

[Trudy Claspill]

We really need to see the details of your Automation Rule to provide better guidance.

You said the rule is running every 2 days. Does that mean you are using the Schedule trigger? Are you using a JQL filter with the trigger in that case? 

[Dave Symonds]

Here is the latest version

[Trudy Claspill]

What is the Scope of your Rule (from the Rule Details tab)?

What are the details of the Schedule Trigger?

[Dave Symonds]

[Trudy Claspill]

You don't need the three conditions after the trigger.

The first two conditions (indicated by "1") can be incorporated into the JQL statement in the trigger.

The third condition (indicated by "2") is already in the trigger. You don't need to have that there at all.

If there are less than 1000 issues in the project that meet all three conditions, your rule should not be throttled.

[Dave Symonds]

Bingo - I just looked at that and had the same idea - thanks heaps