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>)
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
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 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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.