Sprint end date notification

[Petr AST]

Hi there!

Do we have the opportunity to create a notification of Sprint End Date via automation for Jira or system tool?

I would like to receive a notification, for example, 7 days before the end of the sprint, in order to have time to complete it.

Watched this post, but got an error https://community.atlassian.com/t5/Automation-questions/Sprint-end-date/qaq-p/1467444

Thanks for any help!

[Tinker Fadoua]

@Petr AST 

Notifications are related to Workflow changes by creating event listeners

May be by using a plugin. However Jira out the box doesn't send notifications related to Sprints.

All the best,

Fadoua

[Petr AST]

@Tinker Fadoua 

Thanks for your answer!

Yes it is, but maybe there is an opportunity to pick out the end date of the sprint, I could not get it yet(

[Tinker Fadoua]

@Petr AST  did you try a JQL? Then a subscription to get the email directly?

[Petr AST]

@Tinker Fadoua 
After some time, I managed to output the value {{sprint.endDate}} in the desired format in a new field, after that, using the rules, I created sending notifications if the task had not yet been closed. Let's check how it will work.

[Bill Sheboy]

Hi @Petr AST 

I am curious: how long are your sprints such that 7-days notice prior to the end helps with completion?  What problem are you trying to solve?

Let's say your sprint is 2-weeks in duration.  Waiting 7 days may be too late.  Perhaps observing the board daily during the daily scrum would help stay on track, with a longer, mid-point conversation on "how are we doing meeting the goal?"

Kind regards,
Bill

[Petr AST]

Hi @Bill Sheboy 

Yes, you are right, I agree with you, there is no such a big deal issue, but to my colleagues or managers it won't hurt anyway. Extra notifications in that case, why not?  And it became like a small challenge.

Ok, I got it anyway, as I said above, I created a few rules to write SprintEndDate to custom date field and then schedule notifications, if it's time.

In general, I would be interested, from your practice, what automation elements can be applied to sprints? My imagination was only enough to warn about the duedates and in case all the tasks were completed?

[Bill Sheboy]

Thanks for that information, Petr.

For the sprint-triggered events, you can get at the smart values.  But that often does help in use cases like yours; for that, a scheduled trigger with JQL on the openSprints() would be better to find and then access the sprint attributes.

For the other case you noted (all tasks completed) you could instead let the actions on the task trigger the rule, and then access the fields via its sprint field.