As part of automating a workflow, I have a rule that's creating a ticket and populating its summary with the summary of the triggering ticket. I'm trying to use a smart value for this, but when I do and save the rule (or even if I move the focus to a different field), the smart value ( {{issue.summary}} ) is deleted from the summary field.
Any thoughts on how to workaround this problem? Interestingly enough, the same smart value is not removed from the Description field, only Summary is treated differently..
Hi Alexander - Welcome to the Atlassian Community!
Try using {{triggerIssue.summary}}
That worked and the field liked it! Thanks :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Alexander Kolev -- Welcome to the Atlassian Community!
Context is important for automation rule questions. Please post an image of your complete rule, in one image, and the complete edit issue action.
Until we see those...
In the past, the symptom you describe was an intermittent error in the rule editor where the smart values / expressions entered were cleared from the field when it lost focus. This seemed to happen when selecting a new field to edit from the dropdown list and not selecting outside the dropdown field before making a change. One way to check if that is the problem is to log out of Jira, clear all browser cached data, close all browsers, and then try again.
Another possible cause of this symptom is when a rule gets "glitched"; that is, the underlying JSON has some unresolvable error in it. There appears to be a problem in the editor where frequent edit / publish cycles may corrupt a rule. The fix for that is to disable and exit from your rule, and re-create it from scratch, and test again.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think it's the first thing you mentioned - i.e. when setting the focus on another control, the smart value just disappears from the Summary field
p.s. Not sure how to provide the whole context without attaching several screenshots. At least I cannot find any way of exporting the rule definition for support/troubleshooting purposes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am glad to learn you got it working, and for future rule question context...
You could capture an image of the entire rule with a screen capture tool or a browser addon which support scrolling page capture. Then also post an image of the audit log details showing the rule execution. Together those will help the community see the same thing you are asking about.
Rules can be exported as JSON by a Site Admin. However, I recommend against posting the JSON for an exported rule to help questions. It is more difficult to visualize, and may include information you did not intend to share publicly: email addresses, URLs, business content, etc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The documentation doesn't mention this behaviour https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Create-issue, Imho, this maybe a bug.
Would recommend raising a support ticket with Atlassian for them to check https://support.atlassian.com/contact/, in the meantime, I hope the suggestions from @Tom Mike and @John Funk work for your use case.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The issue occurs because the Summary field may have stricter validation rules or restrictions in your automation tool. To resolve this, you can define a variable (e.g., {{summaryVar}}
) to store the value of {{issue.summary}}
and then use {{summaryVar}}
in the Summary field. Alternatively, check if the triggering summary contains special characters and use smart value functions like {{issue.summary.replace("special_char", "safe_char")}}
to sanitize them. Additionally, ensure the Summary field is not configured to reject dynamic inputs in the automation or workflow settings. If the problem persists, it may be a bug, and you should report it to the support team for your automation tool.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Tom Mike -- Welcome to the Atlassian Community!
Please do not post bot-generated content without fully disclosing it as such. For more information, please see the community guidelines: https://community.atlassian.com/t5/custom/page/page-id/rules-of-engagement
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Alexander Kolev ,
When you say the smart value is deleted from the field, does this happen only for the smart value of the whole string in the field - so, "Activation for {{issue.summary}}" or just "{{issue.summary}}" part?
Also, does this happen with some other field as well (except Description), or just Summary one?
Cheers,
Tom
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It happens only for the smart value, the rest of the value remains. I cannot see it reproduce for other fields
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hmm, strange 🤔
I stumbled upon similar behavior, but for select list fields, it was never for Summary. Have you tried using different browsers to see if it's also happening there?
You might also try to use {{triggerIssue.summary}} but I'm unsure if that will help in this case.
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.