You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We are looking to create a custom notification using the automation tool in Jira. The trigger can be scheduled and the action will be an email notification, this is the easy part.
What I'm wondering is if there is a creative way to list out all the issues that are in unreleased versions, organized by version?
I know we can use the lookup issues action to find all the issues in unreleased versions, but how can I organize them in an email notification so that they are in a list by each version. We would look for something like below:
I'm thinking something with a Lookup Table could help, but not really sure. Ideally this would be as automated as possible, but if we need to add new versions to the rule as they come up, that would also be acceptable.
Thanks in advance for any answers!
If you have an unknown number of versions to report upon, the format you describe may not be possible with an automation rule. Some reasons are you cannot nest branches, and even if you could, there is no temporary storage (like created variables or tables) that persist outside of a branch, and finally that you cannot yet dynamically update lookup tables.
You could get close to your format using a lookup issues action with JQL to gather the issues, sorted on the fix version, and then produce an output table showing the fix version, issue, etc. in that order.
I do not believe that is possible with the out-of-the-box REST API functions either.
If you have access to some engineers on your team, they could probably write a function to do this in other code, and host that as a function for your rule to call. At that point...you might as well have the external function send the report email :^)
Hi @Patrick ,
Automation is a good option, but if you just need to trigger this email on a regular basis, using the subscription feature can also suit your needs.