1 answer
1 accepted
I wrote this sample rule. See if this gets you going. Assumption is if any of the child issue has a due date > than parent, then it needs to be flagged.
Therefore, I used max to simplify the logic.
thank you, Vishal!
If the condition matches, the output works fine. But for those issues the condition does not match, empty rows are displayed in my email output, screenshot below:
Is there something like an "else function", so if the condition does not match, do not create a row in the table?
and secondly, I'd like to have a scheduled trigger and not a manual trigger. If I just replace it, the branch reports an error like no issues found.
Do you know how to fix that? Thanks!
Hey @Vishal Biyani
this is the rule that I have created so far
And the html body of the mail I'm currently using is:
<html>
<body>
<table border="1" cellpadding="5">
<tr>
<th>Ticket</th>
<th>Beschreibung</th>
<th>Komponente</th>
<th>Bearbeiter</th>
<th>Fälligkeit Epic</th>
<th>spätestes Fälligkeitsdatum untergeordnete Tickets</th>
<th>Link zum Epic</th>
</tr>
{{#lookupIssues}}
<tr>
<td>{{parent.key}}</td>
<td>{{parent.Summary}}</td>
<td>{{parent.components.name}}</td>
<td>{{parent.assignee.displayName}}</td>
<td>{{parent.dueDate}}</td>
<td>{{dueDate}}</td>
<td>{{parent.url}}</td>
</tr>
{{/}}
</table>
</body
</html>
It is possible that double lookups are causing this issue. The logic can be simplified as below:
- Trigger = Scheduled
- Lookup use JQL:
project = <your project> and issuetype in standardIssueTypes() and issuetype != Epic and parent IS NOT EMPTY and component in (<your list of components)
This will return all standard issues that have a parent Epic - Then in Send Email component, filter out rows and include only those rows that have due date past the epics due date. I have used your format and added 1 more column (child issue key) + condition to filter out rows. The reason to include child issue key is for the end user to easily identify which issue in the epic is past due date.
See if this works for you.
<html>
<body>
<table border="1" cellpadding="5">
<tr>
<th>Issue Key</th>
<th>spätestes Fälligkeitsdatum untergeordnete Tickets</th>
<th>Epic</th>
<th>Beschreibung</th>
<th>Komponente</th>
<th>Bearbeiter</th>
<th>Fälligkeit Epic</th>
<th>Link zum Epic</th>
</tr>
{{#lookupIssues}}
{{#if (due date.isAfter(parent.due Date))}}
<tr>
<td>{{key}} </td>
<td>{{dueDate}}</td>
<td>{{parent.key}}</td>
<td>{{parent.Summary}}</td>
<td>{{parent.components.name}}</td>
<td>{{parent.assignee.displayName}}</td>
<td>{{parent.dueDate}}</td>
<td>{{parent.url}}</td>
</tr>
{{/}}
{{/}}
</table>
</body
</html>
Dear @Vishal Biyani ,
the new rule looks like this:
As I said, the rule execution itself was successful.
An email has been sent but it contains only the headers and no content:
The new html body:
<html>
<body>
<table border="1" cellpadding="5">
<tr>
<th>Epic</th>
<th>Fälligkeit Epic</th>
<th>Ticket</th>
<th>Beschreibung</th>
<th>Komponente</th>
<th>Bearbeiter</th>
<th>Fälligkeit Epic</th>
<th>Link zum Epic</th>
</tr>
{{#lookupIssues}}
{{#if(dueDate.isAfter(parent.dueDate))}}
<tr>
<td>{{key}} </td>
<td>{{dueDate}}</td>
<td>{{parent.key}}</td>
<td>{{parent.Summary}}</td>
<td>{{parent.components.name}}</td>
<td>{{parent.assignee.displayName}}</td>
<td>{{parent.dueDate}}</td>
<td>{{parent.url}}</td>
</tr>
{{/}}
{{/}}
</table>
</body
</html>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.