How to find the Sprint end date for a sprint where two sprints are running at a parallel in the same

Question

Hello Community Members,

In my project, two sprint run at a parallel, where Sprint 1 ends on the last Friday of this month and Sprint 2 will end on the last Friday of next month.

Now I wish to have an automation rule defined where Jira sends email to the team members on the last Thursday of the month to check the status of the tickets which are not in Closed status.

Problem I am facing is Jira is not able to identify the Sprint end date of Sprint 1, which is ending this month, Jira is always taking the end date of Sprint 2, which is ending next month.

Please help me in the jql query and automation rule on how to design this automation for so that Jira is able to identify the last date of Sprint 1 and check the issues whose status is not in closed state and send emails to the assignee to check the tickets and do the needful.

Thanks for your help in advance!

Bill Sheboy · Answer

Hi @Abhishek Misra -- Welcome to the Atlassian Community!

If your sprints have a standard naming convention, this scenario is possible with automation rules, although it is quite elaborate.  For example, if one team's sprints are named "Team Apple Sprint NNN" and "Team Orange Sprint NNN", they could be filtered from the list of sprints and then the end date checked.

Regardless, I agree with @Marc -Devoteam- that this seems like an approach that is concealing the symptom of potential problems, such as:

* using status reporting to manage the Sprint rather than team collaboration
* errors in refinement or planning, resulting in a mismatch between team capacity mismatch with the selected items
* not focusing on the work in the Sprint
* etc.

Perhaps the teams should discuss at a retrospective this symptom and how to address it without an email (that people could likely ignore).

Kind regards,
Bill

Marc -Devoteam- · Answer

Hi @Abhishek Misra

You can check this earlier post https://community.atlassian.com/t5/Automation-questions/Sprint-end-date/qaq-p/1467444 and look at Florians answer.

Otherwise you could revert to the API.

But mainly I find this bad practice in general.

The team should have the responsibility to make sure al items are "Done", or have raised issues on items in the sprint at the scrum maser or product owner.

Email should not be in play.

Look into your organzation and see how to change the process that the teams does this be default in the process, not by sending them an email.