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

Automation rule triggered by issue #1 - creates and links issue #2 - get issue #2's data ??

Edited

Hello, 

Here's my rule:

--Trigger - Issue #1 Created

--Edit fields on issue #1

--Create Issue #2 with a link to Issue #1 (trigger issue)

--Add Issue #2's ID to a Parameter <---- HOW DO I DO THIS???

--Add a comment to Issue #1 Saying "This ticket has been linked to {{createdTicket.id}} - Click here to open {{createdticket.URL}}". 

How do it grab the context from the created ticket (Issue #2) in the automation's scope so I can use the data? 

Thanks for any assistance. 

Jamie

1 answer

1 accepted

2 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.
Apr 07, 2023

Hi @jamie_gordon 

There is a smart value to refer to the most recently created issue or multiple if you create several: {{createdIssue}} and {{createdIssues}}

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--createdIssue--

And so you can use {{createdIssue.key}} for your scenario.

Also please note: when using the Issue Created trigger, that can fire faster than the data is available to the rule.  So it is a good idea to add a Re-fetch Issue action after the trigger, and before any next steps.  That will slow down the rule and reload the data before proceeding.  So, something like this:

  • trigger: issue created
  • action: re-fetch issue
  • ...continue with your rule steps

Kind regards,
Bill

Beautiful. Works like a champ. 


Thanks so much 

Jamie

Like Bill Sheboy likes this

Suggest an answer

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

Atlassian Community Events