Automation of Recurring Sprints

[Stefan Kløvning]

Hi! I have some recurring monthly tasks that I seek to turn into an automation rule for a monthly sprint. 

I want the automation logic to go something like this: 

1. WHEN: Sprint is completed.
2. THEN: New sprint created
3. THEN: Clone task in completed sprint to new sprint [for all tasks in completed sprint]

Is it possible to create an automation rule like this? I can't find an option like number 2 here to create a new sprint in the automation rules. What other alternatives can there be for automating a monthly sprint like this?

[Ste Wright · Accepted solution]

Hi @Stefan Kløvning 

You could try to create the Sprint using a web request in Automation - check out this answer which can guide you through this process.

Ste

[Stefan Kløvning]

Hi @Ste Wright!

Thank you for the tip. I've started setting up a rule based on the web request, and I get the web request to work. What's missing is to identify the tasks in the previous sprint. I've tried to use the For Each branching method with all connections, but it doesn't include any task. 

Can you tell me how the logic of this automation task works? Does it find the connection based on the action trigger of the rule? I've changed the trigger to manual initiation from a task for testing purposes now, so it would make sense in that case that the tasks from the sprint aren't copied, but shouldn't in that case the task I initiated the rule from be copied?

I would've screenshared a picture of the rule if it was in English, but it's in Norwegian. Here are the steps so far: 
- Trigger: Manual 
- Send POST request
- For each connected task: Create new task, where Summary is copied from last one
- Send email with confirmation

Could you help me figure out how I could adjust it so that all the tasks in the last sprint (identified when the trigger would be that a sprint is finished) would be copied as new tasks which would then be ready to be included in the next sprint?

[Jack Brickey]

Hi @Stefan Kløvning , your observations are correct. There are no sprint Action components. Here is an open suggestion that relates to this - https://jira.atlassian.com/browse/JSWCLOUD-20563