The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation error: Subtasks cannot be associated to a sprint

Jimmy Trivedi
Contributor
May 11, 2023

Already my automation rules are working when I create a new issue, but when I create a subtask, automation rules gets failed.

 

Please see the error log:

is a subtask and subtasks cannot be associated to a sprint. It's associated to the same sprint as its parent.)

 

Automation:

Screenshot 2023-05-12 at 11.40.15.png

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

2 votes
Answer accepted
Alex Koxaras -Relational-
Community Champion
May 11, 2023

Hi @Jimmy Trivedi 

It is exactly as the rule says: A subtask can't take a sprint value since it is a child issue of a task (parent) which belong to a sprint already.

Imagine this: You have a sprint to which you have certain tasks. For a specific task of that sprint, you decide to half the work, by creating two subtasks. It doesn't make any since to add a sprint value to these subtasks, since they are already part of a task which is part of a sprint.

So, you will not be able to assign a sprint value to any subtask in Jira.

Trudy P Claspill
Community Champion
May 12, 2023

Adding to this, I recommend that you add a Condition after the Trigger so that the rule will not continue processing when the created issue is a subtask or an epic.

Screen Shot 2023-05-12 at 2.53.15 PM.png

Jimmy Trivedi
Contributor
May 12, 2023

Thanks for the answer @Trudy P Claspill But it is not working. I've tried it multiple times.

 

PFA

Screenshot 2023-05-13 at 10.08.04.png

Trudy P Claspill
Community Champion
May 12, 2023

Please review the guidance and example. The Condition needs to be directly after the trigger so that the rule will stop before trying to edit a subtask.

Like # people like this
Jimmy Trivedi
Contributor
May 13, 2023
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events