Greetings everyone,
Just to provide a little background - I'm trying to automate some weekly/daily tasks for my team which has been going great.
However, I hit an obstacle with one of the JIRA smart values.
I built an automation that is structured like this -
"Schedule" > "Create New : Task" > "Send Email"
In this last step, I am sending an email to team email that would include smart value {{issue.key}} and {{issue.url}}
Something like this - <a href="{{issue.url}}">{{issue.key}} - {{issue.summary}}</a>
For whatever reason, none of those smart values are being shown in the email sent, neither issue.url or issue.key
Could I get some help regarding this as I am having a hard time trying to resolve it.
Would you please post images of your complete rule and the audit log details, showing the execution of the rule? Those may provide some context for the symptom you are seeing. Thanks!
My hypothesis: you are missing a branch to "most recently created issue" after the task create and before the email send...and so those smart values are empty.
Kind regards,
Bill
Hi @Bill Sheboy
You might be onto something - I haven't used branch rule previously so that might be the reason why this is not working - please find screenshots for rule structure and audit log from latest run.
Also, if you could please provide me with a brief insight of "branch" and its use case just so I can know for the future
And of course, thank you for prompt feedback!
Audit Log :
Rule Structure:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
First thing: your rule is missing a branch on "Most Recently Created Issue"...or you could change your smart values from:
{{issue.summary}} to {{createdIssue.summary}} to reference the most recently created one.
Branches allow you to loop processing over related issues or smart values. You can learn more about them here: https://support.atlassian.com/cloud-automation/docs/jira-automation-branches/
For a higher level overview, perhaps look here first for more on automation rules: https://www.atlassian.com/software/jira/guides/expand-jira/automation
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you both @Bill Sheboy @John Funk
I was able to resolve my issue by using Bill's advice, it works perfectly now!
I even played around a little bit with it after reading an article that Bill has provided me with and I have created even better automatization than I could have thought of!
You guys rock! :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Miloš,
This is what I use, and I know that it works.
<a href="{{issue.toUrl}}">{{issue.summary}}</a>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi John!
Thank you for prompt response, I literally copy/pasted your code and it still does not work for me - I am adding a screenshots of both email that I got and rule that I wrote.
Maybe I am doing something wrong.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Very strange indeed.
I do have access to the issue, attached screenshot of the issue created by this rule I just ran in my previous comment.
I am also a project lead for this project in which the issue is being created so its strange that it does not show smart values.
This is exactly the reason I started the thread sine I've been trying to troubleshoot this for a couple of days now by myself with no luck whatosever.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would go ahead and open a support ticket with Atlassian to see if they can help. Please post the resolution back here so it will help future readers of the post. Good Luck!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's the smartest approach I believe.
Of course, I will update the thread once I find the resolution, thank you for your assistance!
If anyone else of the readers might have another idea, I would gladly try it out.
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.