Im trying to setup the following and I would like to know the steps and the exact syntax to set it up
1. The rule needs to triggered manually by an user everytime
2. The rule is to fetch the list of items from the upcoming release board which are in "In Progress" or "Done" status.
3. Send the list in one email to users
4. Even if the rule was triggered after few minutes and there are no changes made, the list needs to be sent again.
Hi Aaron,
Thanks for the quick revert. I will test and confirm the results.
Thanks,
Akila
Just to make sure I'm clear.
You want a manually triggered automation, that takes any issues that are in the statuses "in progress" or "done". This bit I understand but I have a few questions.
Who do you want the results emailed to? The user who triggers the rule? And aids from the status do you want them sent only the tickets they are assigned to? Or just any tickets in the statues mentioned.
If you can clarify that for me I should be able to create something for you.
Thanks
Aaron.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Aaron,
Thanks for getting back.
So i have a release board with 5 tickets tagged to it. I want to manually trigger a rule for the release board to send one email with all the 5 tickets listed to a group of users.
The email should have the following columns:
Issue Key, Summary, Status
I cracked the part to send the email however 5 different email goes out instead of one.
Hope this helps.
Thanks,
Akila
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That does help.
I think this can be solved with an "issue lookup" action. You should be able to loop through them using the issue lookup loop function.
I will test this for you later on today and if I get that bit working will send the structure your way.
Thanks
Aaron.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
<table border="1"> <tr> <th>Issue Key</th> <th>Summary</th> <th>Status</th> </tr> <tr> <td>{{issue.key}}</td> <td>{{issue.summary}}</td> <td>{{issue.status.name}}</td> </tr> </table>
This is the syntax i used, however, i am not sure how do i fit in the "lookup issue" to this and one list to be sent as an email
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think I've achieved what you need.
Using the issue lookup action and then the {{#lookupIssues}} smart value.
You can adapt the automation to fit your needs but as you can see from the output it does as you want.
Thanks
Aaron
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Aaron,
That works like a magic. Need few more help. I tried to further enhance it such as output in table format, alignment etc. this is the modified query on top of yours, however, it is not aligning properly. Need your help again.
Also, i have added custom statuses to the ticket flow. Instead of returning the status like Open, In Progress, Done, it comes as number. How do i fix it?
<table border="1">
<tr><th>Issue Key</th> <th>Summary</th> <th>Status</th> <th>Build Version</th> </tr>
{{#lookupIssues}}
<tr> <td>{{Key}}</td> <td>{{Summary}}</td> <td>{{Status}}</td> <td>{{Build Version}}</td> </tr>
{{/lookupIssues}}
</table>
Thanks,
Akila
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Aaron,
I was able to resolve the status returning numbers instead of the actual status number. I used {{status.name}} instead of {{status}} and that did the magic.
Now all i need is how to add header to this query so the output will have table headers.
<table border="1"> {{#lookupIssues}} <tr> <td>{{Key}}</td> <td>{{Summary}}</td> <td>{{Status.name}}</td> <td>{{Build Version}}</td> </tr> {{/lookupIssues}} </table>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm not so great with HTML, so you may need to use some AI to help you out on that one.
Unless someone here can chip in for you.
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.