Ability to add tasks to current or future sprints

[Mike Underell]

I would like the ability to add recurring tasks to current or future sprints from within The Scheduler please. This would cut down on a lot of repetition for myself and my team.

Thank you!

[Łukasz Modzelewski]

Thank you for your proposal - we already have it in our backlog :)

Server version of The Schedule supports this feature and we would like to implement this also in cloud version.

Currently we are focusing on making sub-tasks available in cloud version.

Best regards,

Łukasz

[Former user]

Hi.

Apparently this improvement has been raised several times over the last 4 years. The last comment suggests that it should have been done last year, but I still can't see it.

Can you please give me an ETA when this will be available?

Thanks!

[Łukasz Modzelewski]

Actually it is possible, it appears that this ticket was not updated at the right time – I’m very sorry for that.

You can add Scheduled Issues to current and future sprints:

You need to remember to change this field when sprint is no longer active.

On our Roadmap, we have feature allowing scheduling issues in ‘currently’ active sprint:

https://trello.com/c/HJ7MJgzE/12-ability-to-add-scheduled-issue-to-the-currently-active-sprint

Please watch, vote or add a comment on the features you like

Cheers,

Łukasz

[Carolina Camilo]

This is great! But not what I was hoping for, as one has to still manually address repetitive tickets - aka update the sprint when the sprint is no longer active.

Rather than specific the exact sprint, one of the options in the dropdown should be 'current_sprint' which acts like a search query and at the time the ticket is created will assign the ticket to the current sprint (or fail if there is no active sprint at that time).

Thanks!

[Łukasz Modzelewski]

As a workaround you could create few clones of Scheduled Issue and set them to appropriate sprint, while setting up the execution start / end dates matching sprint start / end dates. This could work if you have constant know sprint periods.

The downside is that if you decide to make changes in the scheduled issue for sprint 2, then you would have to apply this changes to those already cloned scheduled issues (for upcoming sprints 3,4...)

PS. With dropdown option for the 'current' sprint there is also a problem with 'parallel sprints' as there could be 2 active sprints at the same time: https://confluence.atlassian.com/jirasoftwarecloud/using-parallel-sprints-797737030.html