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,072
Community Members
 
Community Events
184
Community Groups

Jira Automation - Linked issue if they are in the same sprint

I am doing some rules the idea si the following:

When an issue is created it should make the following checks:

1.If the type is BUG
2.If there are linked issues to it 
3.If any of the linked issues are part of the current sprint.

In that case if all 3 match , it should set the Sprint of the bug to the current sprint. I am receiving an error though , any help ? 

TinyTake20-03-2023-11-15-49.pngimage_2023_03_20T20_19_50_824Z.png

3 answers

2 accepted

0 votes
Answer accepted
Bill Sheboy
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.
Mar 20, 2023

Hi @Georgi Nikolov 

Adding to the other answers provided...

The Issue Created trigger can happen so quickly that the data is not yet ready for other things, such as conditions and actions, leading to unpredictable results and rule errors.

When using the Issue Created trigger, it is a good idea to immediately follow that with the Re-fetch Issue action before performing any other steps.  This will slow down the rule by reloading the data, helping to confirm steps work as expected.

Kind regards,
Bill

0 votes
Answer accepted
Juan Carlos Vera
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.
Mar 20, 2023

@Georgi Nikolov ,

Try to put this JQL condition for the Sprint restriction, instead of "Issues in the sprint present"

sprint in openSprints() 

Same error with this one.

0 votes
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.
Mar 20, 2023

Hello @Georgi Nikolov 

Can you provide a screen image of the details of the condition (IF: all match)?

I suspect that the problem is the third element of that condition but I would like to see the details.

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.
Mar 20, 2023

The condition:

Related issues: Issues in current sprint: present

...is trying to confirm that there are other issues in the same sprint as the trigger issue. Since the trigger issue is not currently in a sprint, this produces an error. It also doesn't match the condition that you said you wanted which is

If any of the linked issues are part of the current sprint.

In that statement what are you referring to when you say "current sprint"? 

Like # people like this

I managed to do it with Linked issues present and "

sprint in openSprints() 

" as stated in the previous comment. Thank you all!! :) 

Suggest an answer

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

Atlassian Community Events