jira automation - send email of issues still open on current sprint

Laura Hanna
Contributor
December 4, 2024

I understand how to export issues within a sprint and writing the sql for this. But, I have to manually enter in the "sprint name" sprint = "Sprint 1"

 

I want to be able to automate an email of the list of stories still open in the current sprint.

Or when the sprint is about to close... Say - 2 days. This way I can notify the users to work on the stories that they may have forgotten about etc.

Is there a smart value of "current sprint".

There is a "Sprint Create", "sprint complete" and "sprint started" so none of these triggers would work for me...

3 answers

2 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 4, 2024

Hi @Laura Hanna 

You note a team using Sprints, and so they are likely using Scrum practices also.

Rather than sending a reminder email, why wouldn't the team already know which User Stories are done (or not) when they have their Daily Scrum (i.e., standup) together?

Kind regards,
Bill

Laura Hanna
Contributor
December 5, 2024

This is a new group learning agile. And sometimes they need a little nudge...

0 votes
Aron Gombas _Midori_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 5, 2024

Actually, you could use saved filters with subscriptions and the "openSprings()" JQL function. For simple situations, it may be simpler than managing an automation rule.

0 votes
Answer accepted
Mikael Sandberg
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 4, 2024

If you only have one open sprint at the time in the project then you can use the openSprints() to find the issues that are still open. There is no trigger in automation that can get the end date of the sprint, but you could work around it by using the scheduled trigger and then use the smart value as @Bill Sheboy mentioned below.

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 4, 2024

Hi @Mikael Sandberg 

FYI...once the issues are read within an automation rule (e.g., with Lookup Issues action and JQL) the sprint field in the first issue could be filtered for the "active" one to get the sprint's end date:

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

That value could be stored in a variable for additional adjustment / comparisons.

Kind regards,
Bill

Like Mikael Sandberg likes this
Mikael Sandberg
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 4, 2024

Ahh, I forgot about that, thanks for pointing that out @Bill Sheboy. I changed my reply accordingly. 

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer