Jira automation. Reminder for users - forcing them to be active

[Maksym Kyreiev]

We have a problem - people who create tasks are not very actively involved in their further verification or testing. For example, we received a task, then the programmer asked a question or solved a problem and submitted it for testing, and the task can wait several days until the user responds to our question or comment. The project manager has to run after them and remind them to get on with the task. It is very uncomfortable. I want to set up an automation rule in the JIRA ATOMATIOM, that will:

1. Check how much time has passed since the programmer’s last comment,
2. If more than one day has passed AND If the status of the task differs from “DONE”, an automatic comment with a reminder should appear in the task and this should continue until the user leaves a comment and changes the status of the task.

I can't find how to bind to the date of the last comment from a specific user. All I found in automation was the task update date, but this doesn’t suit me. I would appreciate any help/advice.

[Vinu · Accepted solution]

Hi @Victoria Danner

Its best practice to have close out the sprint before the sprint end date and finish it off with your scrum calls.

Then before starting your next sprint its always advisable to reel in your team for the sprint planning session where you classify your issues and then you the sprint manager can start the sprint.

There are several Atlassian documents on how to plan sprints and its best practices. This should help you align your organization's scrum process with the established best practices.

https://www.atlassian.com/blog/agile/sprint-planning-atlassian

https://www.atlassian.com/agile/scrum

[Victoria Danner]

Thank you!  I will refer to these documents.  I was also interested if there is any impact to reporting (like Sprint report, Burndown) with end/starting sprint on same day (thus, there is an overlap of activity).  

[Vinu]

It wont allow you to set the start date as to be the same as the end date. Start date of the sprint must be before the end date. And eventually your total number of working days in the sprint will be zero which does not make much sense :)

[Carolyn Hinkel]

When I start a sprint, I'm using the start date/time of 12:01 am cst and an end date of 11:59 pm cst.  Is this necessary to do or should I close the current sprint and then start the next after the planning session?  I'm concerned that there is a gap in time that could affect reporting if the sprint end and start dates don't align.