Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,556,502
Community Members
 
Community Events
184
Community Groups

Automation error: Subtasks cannot be associated to a sprint

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

2 votes
Answer accepted
Alex Koxaras _Relational_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
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 Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
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

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

 

PFA

Screenshot 2023-05-13 at 10.08.04.png

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
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

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events