Hi I want so send an personalized Email within a rule and address it to the ticket assginee. Neither of the following Jira Smart values is working. Did someone experienced this before?
See the workflow attached
Best
Nils
Based on the rule you are showing, I hypothesize your trigger does not have JQL as you want to send one email with a list of issues for each assignee.
If that is correct, your email body is referencing the {{issue}} smart value, but that is not available. For your case, I believe you should use the expression:
{{lookupIssues.first.assignee.displayName}}
Also please note: your branch variable appears to be named distinct. It is a bad idea to use variables with the same names as existing smart values and rule functions, such as distinct. The reason is they could collide with other values, leading to unexpected and undefined behaviors.
I recommend adding a prefix to all variable names to prevent this problem, such as:
varDistinct
Kind regards,
Bill
@Bill Sheboy thanks again. It worked. From where do you have this knowledge? I quite often experience things like this. I read the docu try to implement something according to it just to get stuck, because if you do things little different jira has a whole different behavior.
tbh I find this quite annoying...
But thx so much!
Bets Nils
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Awesome; I am glad to learn that helped!
On automation knowledge, I agree the documentation has gaps and continues to improve over time. My ways of learning about this product are:
Happy rule writing!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey, thank you so much for the detailed answer. I will have a look into these pages before I address my issues here :D.
But I am sure you will hear from me soon haha.
Best
Nils
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nils,
Those smart values should work according to the documentation.
What's the result? I think you forgot to include that in your question.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The result is just an empty field. So it displays nothing
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.
Same issue with me, {assignee.displayName}} not giving any output in slack and email messages
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Raj_ Rohit -- Welcome to the Atlassian Community!
Context is important for automation rule questions.
I recommend creating a new question, linking back to this thread, and in your question include the following:
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.
Bill,
I am creating automation rule and in my rule I am detection action of task created and once task created I am sending automate email using following smart value
*New Vendor request has been created*
1. Name: {{ issue.summary }}
2. Reported by: {{issue.reporter.displayName}}
3. URL: {{issue.url}}
4. Assigned To: {{assignee.displayName}}
In email output, all aforementioned 3 fields are populating however 4th one is reflecting black value in outcome.
However if I use action, task transition or task change then all fours values are populating in email body. this is totally a bug in Jira.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please post an image of the audit log details showing the rule execution.
Does the issue have any assignee at the time rule executes?
Finally, your rule appears to use the Issue Created trigger. That trigger may fire so quickly that some data issue data may not yet be available to the rule. The solution for that symptom is to always add the Re-fetch Issue action immediately after the Issue Created trigger. This will slow down the rule a bit and reload the data before the rule proceeds.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ditto - I have a field called "Vendor Name" and am using the smart value {{issue.Vendor Name.displayName}} in a number of comment automations, but it's spitting blanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Smart values are name, spacing, and case-sensitive...and, they often do not exactly match the display name of the field on the Jira pages. When an incorrect smart value is used, that collapses to null, and often does not work as expected.
To learn the correct smart value (or custom field id) for your field, please use this how-to article: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/
If that does not help solve the problem, please create a new question with "Ask the community" at the top of this page, including images of your complete rule, the relevant actions / conditions, and the audit log details showing the rule execution. Those will create context for the community to offer suggestions.
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.
@Amy Chamberlain - It is better to create a new question so that more people will see it and answers can be tailored to your specific issue.
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.