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 to move an issue into a sprint when reaching the due date

Marije Pierson_mp8lqt

I'm feeling a bit dumb because I don't understand how to fix the error I'm seeing, help would be appreciated!

This is the automation:

Screenshot 2022-10-18 at 11.49.15.png

Screenshot 2022-10-18 at 11.49.20.png

Screenshot 2022-10-18 at 11.49.27.png

Then, this is the error. With my test issue being IPDEV-451. It looks like IPDEV-451 passes but nothing happens:

Screenshot 2022-10-18 at 11.50.37.png

Am I supposed to be putting in some other kind of check to ignore the other issues that or a different type of condition check?

Accepted answers

Walter Buggenhout

Hi @Marije Pierson and welcome to the Community!

In you automation condition you are looking for issues in status to do. Then, later on, you are trying to transition them to that same status.

It might solve your problem to just choose edit issue instead and then just update the sprint field.

If you do have a transition going from the current to do status to that same to do (which is possible), than you should create a screen (in Jira admin > issues > screens), make sure the sprint field is on that screen and then associate that screen with this workflow transition. But I assume the first option would be a lot simpler to implement.

Hope this helps!

All comments

Patricia Francezi_iDev_

Hi @Marije Pierson

Error message says there is a transition screen when you move to "to do" status.

You can try to change the status mannually and check this.

Automation dont fill fields when there is a transition screen

Walter Buggenhout

Hi @Marije Pierson and welcome to the Community!

In you automation condition you are looking for issues in status to do. Then, later on, you are trying to transition them to that same status.

It might solve your problem to just choose edit issue instead and then just update the sprint field.

Hope this helps!

Bill Sheboy

Hi @Marije Pierson -- Welcome to the Atlassian Community!

Two more ideas, in addition to what has already been suggested...

When you have a question about an automation rule, please post an image of your complete rule. That may provide context for what is happening, and the structure of the details you have shown.

Next, I am trying to understand your use case and what problem you are trying to solve. Are you intending to add issues to a future sprint or to the active one on a schedule? For an active sprint, wouldn't that create problems for the plan the team has already created, based on what they believed was possible to finish in sprint planning?

Kind regards,
Bill

Marije Pierson_mp8lqt

Thanks Bill - by complete rule, do you mean this one?

Screenshot 2022-10-19 at 09.09.39.png

We occasionally have work that needs to be done by a future date and want it to be automatically added to the current sprint when the due date is reached. Currently, it can't be added to a future sprint because they're often not yet setup.

I know it's not a proper way to manage something like this but they're low volume and an easy way to not forget something. I could switch it to send a notification on the due date to remind us to add it to a sprint, I guess.

Marije Pierson_mp8lqt

I'll give that a try, thank you!

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud