Hi
I am trying to write an automation rule that adds a comment to an issue if the Treatment field has more than one option selected. The comment must @mention the Assignee and Reporter.
If the issue is assigned to a user, it works perfectly but if the issue is unassigned then I get the attached error. I do not want the accountid to be displayed in the Comment if the issue is unassigned. Does anyone know where I am going wrong in my automation rule?
I rewrote the automation rule and split up the actions based on each of the conditions, and it now works.
Thanks @Bill Sheboy for your suggestion. I tried it out with and without an Assignee and unfortunately without the Assignee still displays the accountId. I have attached a screenshot of both scenarios
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This seems to indicate the assignee is blank versus null, which I thought was fixed so both could evaluate to EMPTY with the REST API and JQL queries.
I recommend working with your site admin to submit a support ticket for this to have Atlassian take a look: https://support.atlassian.com/contact/#/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Kasturee
It seems there are some missing curly brackets for that format of the conditional logic. Or if the assignee previously had a value and it is no longer evaluating to null.
Perhaps try one of the other forms of "if":
{{#if(not(issue.assignee.isEmpty))}}[~accountId:{{issue.assignee.accountId}}]{{/}}
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.