JIRA Description Automation

CG
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 25, 2022

Hi there,

I am currently trying to set up a new automation within JIRA which basically works as follows:

  1. Trigger: issue created
  2. Action 1: update the Description to include some extra details
  3. Action 2: clone the issue in a different project. Within this new ticket I need the description to include:
    1. Original issuekey
    2. The description (as updated in step (2))

In the cloned ticket's description, I am successfully getting the issue key. However I am not managing to show the description that I had updated in step (2). 

I am using the following code within the additional fields section:

"fields": {
"description":"original issue {{issue.key}} updated description {{issue.description}}"

Any help please? Am I using {{issue.description}} correctly, or maybe do I need to add another component to make sure it gets the updated Description?

TIA

Screenshot 2022-04-25 at 17.21.14.png

2 answers

1 accepted

2 votes
Answer accepted
Filipi Lima
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 25, 2022

HI, CG! Welcome to the Atlassian Community!

After editing the issue, the smart value will still refer to issue.description as being the original information on it.

After running step 2, try adding another action: Re-fetch issue. That should give you the most recent value for the description.

Let us know how it goes!

Also, here's a bit more info on the re-fetch issue action, if you want:
https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/

Cheers,

Filipi Lima

0 votes
Guilhem Dupuy
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.
April 25, 2022

Hi @CG ,

 

I think I get this one ! It's probably because you nee to re-fetch / re-actualize your issue data between the action where you set a new value for the description field (step 2) and the moment you clone the issue (step 3).

Otherwise Automation doesn't get it and you'll find the old description value in your cloned issue :)

Just add an automation action called re-fetch issue data between steps 2 & 3 and it should work  !

 

Let me know if it helps,

Guilhem

Suggest an answer

Log in or Sign up to answer