Issue in table generation through Lookup Issues Automation

Question

Hi Team,

I have created an automation for Lookup Issues in Jira Data Center with an JQL & an email will sent to the Assignee, Reporter & Watchers of the ticket present in the Jira Tickets of the JQL within a table. The Jira Tickets data will be sent to them in a Table.

The thing is that everything is working fine but the table which is getting generated is having many extra boxes & spaces in it. I have run the same code by creating same rule in Jira Cloud but over their everything looks fine & clean & table generated is also clean.

I am attaching screenshot of the Table which is getting generated in email in Jira Data Center. Also attaching the Screenshots of the Automation & Code written withing the Automation to generate table.

Please help me over this.

Thanks & Regards,

Yash

Yash Sheetal Bhandarkar · Answer

Hi Bill,

Please find my reply for every question you asked -

First thing, what problem are you trying to solve by running this rule every 5 minutes?  That seems like it would be overwhelming to the recipients.

When running the Automation Rule for Lookup Issues, the table in which we want the data to be sent to the users using Email, its showing empty boxes in the Table as shared in the above discussion description.

Next, as your rule is written it will send the email multiple times.  This is because the trigger has JQL without the option selected to "simply run the conditions and actions without providing the issues."  The fix for that is to either enable that option, or remove the JQL from the trigger (and add a condition after the Lookup Issues action to check for results).

Okay, I will remove that JQM from Trigger.

The fix for that may be to remove the conditions for Issue Type, Key, and Summary, and replace the one for Assignee with this:

Can you please elaborate this in detail so that I can make changes accordingly in the Automation ?

Thanks & Regards,

Yash

Bill Sheboy · Answer

Hi @Yash Sheetal Bhandarkar First thing, what problem are you trying to solve by running this rule every 5 minutes? That seems like it would be overwhelming to the recipients. Next, as your rule is written it will send the email multiple times. This is because the trigger has JQL without the option selected to "simply run the conditions and actions without providing the issues." The fix for that is to either enable that option, or remove the JQL from the trigger (and add a condition after the Lookup Issues action to check for results). What is the purpose of the conditional logic in your HTML, as every one of those fields except the Assignee will definitely have a value? Perhaps there is a problem with the conditional HTML getting confused with the smart value syntax for conditional logic: https://confluence.atlassian.com/automation/jira-smart-values-conditional-logic-1081351607.html The fix for that may be to remove the conditions for Issue Type, Key, and Summary, and replace the one for Assignee with this: {{assignee.displayName}}{{#if(not(exists(assignee.displayName)))}}Unassigned{{/}} That will always include the Assignee's displayName, if it exists, and when it does not, use Unassigned. Kind regards, Bill