The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Smart Value to use, please help

Earl Kabiling
September 23, 2020

Hi, 

I've set up an automation where when an issue is created in (SD-XXX) Jira (matching the JQL condition) it will create a new issue (as a bug) in another project DEV (PRDS-XXX) for escalation to the developer then it will trigger an email to the dev group email. 

The automation is working but my problem is when it triggers the email it's showing the SD-XXX {{issue.key}} but not the project (PRDS-XXX). 

What smart value should I use in this case to show the DEV PRDS-XXX issue key instead, in the triggered email?

Thanks, appreciate your help!

The automation below

smart value.jpg

 

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Answer accepted
Dirk Ronsmans
Community Champion
September 23, 2020

Hi @Earl Kabiling ,

perhaps I'm missing something but wouldn't you be able to just take it out of the automation and use the DEV project's notification scheme to accomplish this?

There you would have the Issue Created event which triggers an email.

Or is there a specific case why you are using the Automation for sending the email?

Dirk Ronsmans
Community Champion
September 23, 2020

Now if you really need this through the automation you can do it as follows (cause I don't think you can get the smart value without some additional queries):

You add a Branch/Related issues component and send the email from there.

 

image.png

 

Your Brand rule would look similar to this: (you can use all created issues or most recently created)

image.png

Like Earl Kabiling likes this
Earl Kabiling
September 24, 2020

ahh that makes sense, thanks  @Dirk Ronsmans both of the solutions you have recommended works :)

Much appreciated!

 

Earl

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events