Automation for Spillover Subtasks

siva_vemula
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 3, 2025

Hi There,

I Subtasks on the stories .

I am looking for a Automation Rule which track Stories that spill over into the next Sprint, ensuring that any Sub-task that isn't completed gets marked as Spillover = Yes. when the sprint is closed.

2 answers

1 accepted

1 vote
Answer accepted
Vishal Biyani
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 3, 2025

@siva_vemula 

You can try below automation rule

snip.png

siva_vemula
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 3, 2025

Hi @Vishal Biyani  Thank you so much. If the subtasks is NOT DONE, the issue filed Spillover should be updated as YES and if the Subtask is DONE the issue filed Spillover should be updated as NO.

Can you review and correct

image.png

Vishal Biyani
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 3, 2025

in that case in Issue matches JQL use issuetype in subTaskIssueTypes()

Then add another if Issue matches JQL condition: 

check statusCategory = Done

then edit issue fields to set Spilled Over = No

Then add another if Issue matches JQL condition: 

check statusCategory != Done

edit issue fields to set Spilled Over = Yes

0 votes
siva_vemula
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 3, 2025

@Vishal Biyani  Can you help with the screenshot please 

Vishal Biyani
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 3, 2025

@siva_vemula 

Can you make the change and share the screen shot of what you have done?

if you hit an issue, I will be happy to help. However, for your own learning, I encourage you to try this out yourself first

siva_vemula
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 3, 2025

image.pngKindly validate 

Vishal Biyani
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 3, 2025

I think what you can do instead of having 3 if condition, 

in 1st condition, use issuetype in subTaskIssueTypes() and statusCategory = Done

then edit issue

in 2nd condition, use issuetype in subTaskIssueTypes() and statusCategory != Done

then edit issue

 

that will ensure that both ifs are evaluated correctly.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events