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, initial run across all issues

Malte Larsson

Hi,

I've created an automation rule that sets the Due date of issues based on sprint they belong to. The rule is triggered when the issue is updated in any way.

Is there a way for me to execute this rule one time across all existing issues within the project in order to avoid having to manually update each issue individually?

Kind regards
Malte

Accepted answers

Dirk Ronsmans

Hey @Malte Larsson ,

My main train of thought we be the following:

Duplicate your automation rule
Change the trigger to run scheduled
Enter a proper JQL on which it needs to run (could be just Project = xxx)
Sit back and look at the result after the schedule has run

All comments

Dirk Ronsmans

Hey @Malte Larsson ,

My main train of thought we be the following:

Duplicate your automation rule
Change the trigger to run scheduled
Enter a proper JQL on which it needs to run (could be just Project = xxx)
Sit back and look at the result after the schedule has run

Bill Sheboy

Hi @Malte Larsson

Would you please explain why you want to run this rule for all issues in the project? For example, are you pre-assigning all issues to sprints far into the future?

If not, perhaps changing the trigger to sprint started for the update would help. You may need a "clean-up" rule in the event your team adds/removes issues to/from an already in-progress sprint.

Kind regards,
Bill

Malte Larsson

Hey @Dirk Ronsmans

Perfect! Just the type of solution I was searching for.

Thank you for your help!

Malte Larsson

Hi @Bill Sheboy

I've added an automation rule that assigns issues certain information based on the sprint it's added to. I've added this rule in projects that already have a lot of issues, so I needed a way to trigger the automation rule on all existing issues that already are connected to a sprint.

Dirk had a working suggestion above.

Your comment and effort to help is much appreciated!

Kind regards,
Malte

Anthony Amirfar

Hello,

I'm attempting to do the same thing but I'm confused as to how to make this rule run on every issue in my project.

Would either of you be willing to describe this a little more? Specifically step 3.

See below what I currently have (sorry in advance for my newbie questions)

Bill Sheboy

Hi @Anthony Amirfar

First thing: this is a very old thread, and so I recommend creating a new question, and perhaps linking back to this one. That will ensure the maximum number of community members see it to offer suggestions.

Until we see that new question...

First, your rule should probably use an if / else condition structure rather than what you show: https://support.atlassian.com/cloud-automation/docs/jira-automation-conditions/#If-else-block

Next, please re-read the original steps described by @Dirk Ronsmans , where the rule is copied, the new rule's trigger is changed to scheduled, with JQL to find the issues you want to update.

Specifically, that JQL creates the "stopping condition", where the rule will keep finding issues to update until done. In your case, that appears to be the presence of values in the Parent and Type of Request fields.

Kind regards,
Bill

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

atl-orange