You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
I have an email report consisting of issues resulting from a JQL query.
I'm being asked to separate this list by status into different tables in the email.
I'm wondering if there is a way to apply some form of conditions to the issues loop to restrict to a specific status and then do that as many times as needed to get the separated status tables.
the loop right now is basic as shown below. But can I somehow restrict each loop to a specific status?
{{#issues}}
<tr style="border: 1px solid black;">
<td style="border: 1px solid black; padding:5px 10px 5px 5px; "><a href="{{toURL}}">{{key}}-{{Summary}} </a></td>
<td style="border: 1px solid black; padding:5px 10px 5px 5px; ">{{status.name}}</td>
<td style="border: 1px solid black; padding:5px 10px 5px 5px; ">{{assignee.name}}</td>
<td style="border: 1px solid black; padding:5px 10px 5px 5px; ">{{updated.format("yyyy-MM-dd")}}</td>
</td>
</tr>
{{/}}
</table>
Any help or suggestions would be appreciated.
Thanks in advance,
Greg
Hi @Greg Bailey ,
unfortunatelly, I don't think this is possible.
What about to sort the issues by status, would it help a little bit?
The second possibility I can see is to send more emails, for each status one email, but that's not very nice solution.
Hi Hana,
Thanks for that. I had a feeling it may be the case this was not possible.
yeah, the emailed report is already sorting by status so we at least have that. And no we don't want to send multiple emails. ;-)
Thanks for the response,
Greg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Greg Bailey
How about this approach:
<ul>{{#lookupIssues}}<li><a href="{{url}}">{{key}} - {{summary}}</a></li>{{/}}</ul>
I tried this with three sections showing the Todo, In Progress, and Done issues listed.
Best regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks so much @Bill Sheboy
I'm out of the office today, but this will be top of my list tomorrow AM.
Regards,
Greg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Color me sad...
we are on Jira Server, not Cloud and the lookup issues action is not available for server.
Back the drawing board. ;-(
btw here's the ticket to bring lookup issues to the server version. Please add votes!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Greg, sorry that I missed you were on server version.
I wouldn't hold out for the server version getting that soon. Atlassian is stopping sales of that product soon (Feb 2021) and will sunset after that (Feb 2024):
https://confluence.atlassian.com/support/atlassian-support-end-of-life-policy-201851003.html
__Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can use Notification Assistant for Jira for this. We support JQL bounded tables as a common email type.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi all, After many months of work, I am delighted to announce the launch of the Jira Automation Template Library! The Template Library is a new website dedicated to all things Jira au...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.