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,467,416
Community Members
 
Community Events
177
Community Groups

The Sprint Created Trigger is not working or running my subsequent issue creation actions.

Edited

I have created a very simple automation that does the below:

 

  1. When a sprint is created.
  2. Create a Story in the same project.
  3. Name the Story as "Retro Actions, {{sprint.name}}".
  4. Specify the Epic link for this story.

 

I have saved and published this automation but when I create a sprint via the backlog "create sprint" button, nothing happens and I receive no error email. From what I can tell this automation is not being triggered at all.

 

Screen Shot 2021-11-18 at 14.00.27.pngScreen Shot 2021-11-18 at 13.58.48.pngScreen Shot 2021-11-18 at 13.58.44.pngScreen Shot 2021-11-18 at 13.58.35.png

3 answers

1 accepted

1 vote
Answer accepted
Curt Holley Community Leader Nov 18, 2021

Hi @Keenan Cassidy 

What is in the detail of the "Some errors" log entry just prior to your last changes?

Also, do you need this rule to respond to another? If not, untick "Allow rule trigger"

and about the only other thing I can think of that may improve this would be to actually specify the project (rather then leaving it as "Same project". I seem to recall that fixing a rule for me, but I can't recall the details, only that I was surprised that was what fixed it.

Amazing Curt! That did the trick! Do you happen to know how I can make sure that this newly created issue is added to this newly created sprint?

Curt Holley Community Leader Nov 18, 2021

Yes, put {{sprint.id}} into the Sprint field of your rule, for each Story you are creating. As the rule is triggered by Sprint creation, that smart value picks up the ID of the sprint being created.

id.png

Amazing! You're the best! Thank you 🙃 ❤️ 

Screenshots added to original question.

0 votes

Hi @Keenan Cassidy -- Welcome to the Atlassian Community!

Would you please post images of your rule, including the details section, and of the audit log showing any executions or errors?  That may provide some context for what is happening.  Thanks!

Kind regards,
Bill

Hi Bill, 

 

Thanks for your quick reply. I have added screenshots of my rule as you requested. Thanks for the help.

Like Bill Sheboy likes this

Thanks for that information.  Would you also please post an image of the audit log?  That will show if there were any errors when attempting the rule.

Look for the audit log at the top-left of the rule definition, and then expand the "show more" links for details.

Thanks!

I found it and added to the top of the original question.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events