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; } } }

About JSM Automation Limitations

As a result of processing many issues with JSM automation, it seems that all of them have not been processed and ended in the middle. If you process many issues with automation, will there be interruptions in the middle?
Are there any restrictions?
Looking at the audit log, the processing time ended in about 600 seconds.

Accepted answers

All comments

How many issues are you trying to process? What is the trigger used by the rule?

The short answer is yes. Especially if you are using the newer automation.

The automation is based on the rate limit here: https://support.atlassian.com/cloud-automation/docs/differences-between-automation-in-jira-server-and-jira-cloud/#

I'm trying to process about 400 issues.

About 400 issues are subject to JQL search.

Does the number of rules that can be processed per month mean the number of issues to be processed?

No, it means the number of times the rule fires.

Can you share the rule? Is it a Global Rule? Or for just one project?

Rules for one project.

JQL specifies updated > "-2w".
The number of hits is about 400.

If it takes too long to complete, if memory serves me well, this could be terminated if it is taking too long to be completed.

As such the recommendation is often reduce the filter to a manageable size and as @John Funk @asked, it’ll be great to know the trigger event

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management