Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Error Failed to close tag

Leanna Bremenkamp June 4, 2025

I am a beginner automation user and what I am trying to achieve is a email using the lookup issues operation.  I want it to return a list of all the items in the project in table form. I keep getting an error that the {{lookupIssues}} tag is not closed. I know its probably right in front of me but cannot figure it out.

 

{{#lookupIssues}}
<table>
<th>Project</th>
<tr>{{summary}}: <a href="{{url}}">{{key}}</a></tr><th>Status</th>
<tr>{{comments.getFromEnd(0).body}} </tr>
<th>Assignee</th><tr>{{assignee}} </tr>)

2 answers

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 4, 2025

Hi @Leanna Bremenkamp 

When building a table with dynamic rows for the lookup results, please try putting the iterator inside of the <table> ... </table> structure.  For example

<table>
<tr>
<th>Key</th>
<th>Summary</th>
<th>Status</th>
<th>Assignee</th>
</tr>
{{#lookupIssues}}
<tr>
<td>{{key}}</td>
<td>{{summary}}</td>
<td>{{status.name}}</td>
<td>{{assignee.displayName}}</td>
</tr>
{{/}}
</table>

 

Kind regards,
Bill

Leanna Bremenkamp June 4, 2025

@Bill Sheboy  The email comes now but I am just getting the headers and no rows.

image.png

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 4, 2025

Please post an image of your entire rule and the audit log details showing the rule execution for more context.

I hypothesize the rule is missing the Lookup Work Items action (formerly called Lookup Issues).

 

Also, as different email apps have different levels of support for HTML, please update the markup used to match what your email tools support.

Leanna Bremenkamp June 5, 2025

@Bill Sheboy 

I used what you had indicated above.  The email shows up with the headers but no data.  From what I see, even though they are called Work Items now, the function behind the scenes is still lookupissues.xxx. 

image.png

email.jpg

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 5, 2025

First thing: while Atlassian is renaming "issue" as "work item", they have stated it will not impact smart values a this time.  And so the smart value for Lookup Issues (or Lookup Work Items if your UX has updated) is still:

{{lookupIssues}}

 

Next, as I hypothesized, your rule is missing the lookup action.  Please add that before you try to use the {{lookupIssues}} smart value.

0 votes
Gor Greyan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 4, 2025

Hi @Leanna Bremenkamp ,
I am using the lookupissues via the following way and it is working, try like this.

{{#issues}}
<a href="{{toUrl}}">{{key}} </a> | {{summary}} <br>
{{/}}

In the end, add this {{/}}.

Let me know if there is any information.

Leanna Bremenkamp June 4, 2025

I couldn't make this work

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events