You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
While using the Automation for Jira Cloud, is it possible to get the key of the issue that was created in the very same automation?
Here's a screenshot of what I'm trying to implement. The issue is created perfectly - I just want to send the Key of the created issue over Slack/Teams/Email without using JQL/Lookup to fetch it.
Try this
The previous issue created in this rule.
{{createdIssue.key}}
Added by: the Clone issue, Create issue, and Create sub-tasks actions
A list of issues that have been created in the rule.
{{#createdIssues}}{{key}}{{/}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @steven_peck
I'd suggest you start a new thread for this query.
But to answer your question: Yes, all created tickets can be accessed. You can use the conditions to filter out the tickets where the issuetype is Service Request and take actions on them alone.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
...for anyone who's reading this thread 3 years later, @Jira Guru 's useful answer is from this page, where there's lots of other smart value info: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm sad that is hard to find again this version of getting (spent 1-2 hours to get this).
If you create more than one in single automation - you can use (even if created in Branch-rule):
{{createdissues.get(0).key}} - for first
{{createdissues.get(1).key}} - for second
etc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.