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...
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.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ahh, I forgot about that, thanks for pointing that out @Bill Sheboy. I changed my reply accordingly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is a new group learning agile. And sometimes they need a little nudge...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.