Automation to Update Start and Due dates based on Sprint Dates

Nick Brotherton

Hello,

I'm attempting to reuse Automation logic from THIS Atlassian thread. However - it does not seem to return the current sprint values if it has been in a previous sprint.

In the screen shot, you can see that it has added 11/19/24 and 11/25/24 as the values. Yet, 11/25/24 and 12/9/24 should be the values from sprint 19.

How should I refine the logic from the linked article to assure we are getting the active sprint values?

Bill Sheboy

Hi @Nick Brotherton 

For a question like this, context is important for the community to help.  Please post the following:

• what type of project is this (e.g., company-managed, team-managed, etc.), 
• an image of your complete automation rule,
• images of any relevant actions / conditions / branches,
• an image of the audit log details showing the rule execution, and
• explain what is not working as expected.

Until we see those...

Next thing, that article is for Jira Server / Data Center, and as you note, does not handle the case of issues in multiple sprints correctly.  Particularly in the unusual case of an issue removed / re-added to the active sprint.

Let's solve this by specifically looking for the "active" sprint.  Assuming we are looking at one single issue, that would be this for the Start Date:

{{#issue.sprint}}{{#if(equals(state,"active"))}}{{startDate}}{{/}}{{/}}

And this for the End Date:

{{#issue.sprint}}{{#if(equals(state,"active"))}}{{endDate}}{{/}}{{/}}

These work by iterating over the sprint field values, filtering to get the "active" one, and then getting the field needed.

Kind regards,
Bill