Jira Automation - Planning tasks automatically by Due date to the sprint backlog

[Dominik Trunk]

Hi, 

our team would like to switch from Kanban to Scrum in perspective. Unfortunately, we have the problem that we often wait for an external input from our collaboration partners, which leads to periods of waiting. Right now, these waiting tasks sit on the Kanban in the "waiting" lane for a while until the external partner has completed their ToDo. This disturbs a bit our board and absolutely does not fit with the planned Scrum process.

So we are now looking for a better solution to organize these waiting times in Scrum. 

One idea we had was to split the activities. First we have a task to bring all the information to the external partner and then we have a second task to remind the external partner some weeks later. This second task stays in the backlog and it would be really helpful if we had some kind of automation with a dependency on the due date. As a result, the reminder task will stay in the backlog until the due date of the task occurs. When the task is due, it should be automatically moved to the next Sprint Backlog. 

Do you know any solutions or similar use cases that can help us to implement this in Jira?

Thank you very much and best regards, 
Dominik  

[Bill Sheboy · Accepted solution]

Hi @Dominik Trunk -- Welcome to the Atlassian Community!

You *could* create a rule, triggered on sprint creation which checks for any issues with due dates during the sprint timeframe, and take action.  Rather than adding such issues automatically to the sprint, you may instead want to notify the team to consider their capacity and the "due date" issues for inclusion in the sprint.

Another option is a scheduled trigger rule, which checks for issues due in the next week, or so, and notifies the team to consider actions/next steps.

Kind regards,
Bill

[Dominik Trunk]

Hi @Bill Sheboy , 

thank you for your suggestions. I think the solution no. 1 could work for us. I'll try this. 

Best, 
Dominik