nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation for Jira Can Take a Long Time to Link Issues

Jeff Gordon_5o0sm2

I have implemented a rule such that when an issue of a certain type is created in a single project I run a JQL to find other issues in the project created by the same reporter within the last twelve weeks. Everything works correctly but it takes a really long time to run. I.e., one run took 30 minutes to link 35 issues. It even takes 15-30 seconds to link 4-5 issues. The net result is the rule quickly becomes throttled due to exceeding its 12 hour allotment (I know I can increase this but...).

I know the JQL takes less than a second so I don't think that's the problem. It's definitely related to how many issues will be linked.

Anyone have any similar experience or ideas on this?

Accepted answers

All comments

Mark Segall

Hi @Jeff Gordon and welcome to the community!

Can you share a screenshot of your rule? That would help identify whether there are any opportunities for optimization.

Jeff Gordon_5o0sm2

Here's the rule.

Mark Segall

Thank you @Jeff Gordon

Your rule seems pretty straightforward to me. However, is it correct to assume that you're using Jira Server? If so, there could be any number of environmental factors that could be playing into your execution times (CPU, RAM, etc.). I would check with your Ops team to make sure that they're not shorting Jira on resources.

Jeff Gordon_5o0sm2

Jira Data Center.

I've switched to using a scriptrunner script as it's able to link the same number of issues in about 15% of the time.