I'm currently facing an issue with the summary display in my Jira cloud automation rule when cloning issues across multiple projects. My Configuration: * Trigger: Issue created (Global Rules) * Added a condition : Components contains of X,Y,Z * Actions:* Clone issue with the following configuration:* Clone issue in Project B : CLONE - From {{issue.key}} - {{issue.summary}} * Clone issue in Project C : CLONE - From {{issue.key}} - {{issue.summary}} The issue is using the smart value {{issue.summary}}, the text into the cloned issue's summary continues to display as 'Autogenerated'. Interestingly, when I use the smart value {{issue.key}}, it correctly displays the ticket ID into the clone tasks which are created across all projects. Requesting to guide me and let me know if i am doing something wrong steps. Thanks in advance . :)

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Smart value {{issue.summary}} displaying 'Autogenerated' : Cloned issues : Jira cloud automation

Purni_c40187

I'm currently facing an issue with the summary display in my Jira cloud automation rule when cloning issues across multiple projects.

My Configuration:

Trigger: Issue created (Global Rules)
Added a condition : Components contains of X,Y,Z
Actions:
- Clone issue with the following configuration:
  - Clone issue in Project B : CLONE - From {{issue.key}} - {{issue.summary}}
  - Clone issue in Project C : CLONE - From {{issue.key}} - {{issue.summary}}

The issue is using the smart value {{issue.summary}}, the text into the cloned issue's summary continues to display as 'Autogenerated'.

Interestingly, when I use the smart value {{issue.key}}, it correctly displays the ticket ID into the clone tasks which are created across all projects.

Automation setup example.png Clone issues.png

Requesting to guide me and let me know if i am doing something wrong steps. Thanks in advance .

Accepted answers

Bill Sheboy

Hi @Purni

The Issue Created trigger can fire so quickly that some of the issue data is not available to the rule when it starts. This will cause things like empty / incomplete fields when the rule runs.

To determine if that is the cause, and to fix this symptom, please always add the Re-fetch Issue action immediately after the Issue Created trigger. This will slow down the rule a bit, and reload the issue data before proceeding.

Please try adding that action and re-testing your rule.

Kind regards,
Bill

All comments

Manne Kjærby - ProProces

Hi Purni.

Overall I believe your automation looks correct.

I'm in bit of doubt in why the issue.summary doesn't show up correctly.

But it could be related to issue reference is getting mixed up as you are creating a new issue (and it then looks at it as branched - I'm not sure, just me thinking out loud)

If I were you, I would try to use this smart value - That is referring the original trigger issue.

Purni_c40187

Hi @Manne Kjærby - ProProces ,

Thanks for quick response . I tried the above smart value {{triggerIssue.summary}} , it seems the same 'Autogenerated'.

1round testing.png

Manne Kjærby - ProProces

Hi Purni.

I just tried the automation on my own instance.

When: issue created
Then: Clone issue into ....
- CLONE - From {{issue.key}} - {{triggerIssue.summary}} - {{issue.summary}} - {{summary}}

And all above smart values shows up with the correct summary.

So, I will reference myself: Overall I believe your automation looks correct.

It might be a bug? - I might have overlooked something. I think you should reach out to atlassian support.

Purni_c40187

Ohk .. Thanks for guiding , I will reach out to atlassian support now may be.

Bill Sheboy

Hi @Purni

The Issue Created trigger can fire so quickly that some of the issue data is not available to the rule when it starts. This will cause things like empty / incomplete fields when the rule runs.

Please try adding that action and re-testing your rule.

Kind regards,
Bill

Purni_c40187

Thanks a lots for guidance !! The above mentioned step works..

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

automation

smart-value