How can I create a custom email notification to list out unreleased fix version issues by version?

[Patrick Cartier]

Hello there!

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:

Version 1

• issue key 1
• issue key 2
• etc

Version 2

• issue key 3
• issue key 4
• etc

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!

[Nic Brough -Adaptavist- · Accepted solution]

This implies that when you update (or create?) an issue, the index is going out of sync with the issue.  This is quite hard to do unless you've got code interfering with the process. 

Could you check what post-functions, automations, listeners and so-on you have that might be breaking the create/update of an issue?

[zaharovvv_suek_ru]

I've seen post function that creates an issue and there is no code to change priority field. It is a really strange behavior.  

May be it happened as I've used a SQL job to update priority statuses of linked issues. But SQL job should not be a source of problem because an issue priority was not changed.

Is there any way to change priority of linked issues if priority of main issue is edited?

For example, I have two issues - "issue A" and "issue B".  "Issue A" has a link to issue "B".

Is it possible to set "Priority" field to "Major" of "issue B", if an user sets "Priority" of "issue A" to "Major"?

I have a chance to use ScriptRunner.

[Nic Brough -Adaptavist-]

NEVER write to a Jira database with SQL, unless it is offline and you know exactly what you are doing (99% of people trying it do not know enough to risk it).  Otherwise you will damage (potentially destroy) your system.

That change almost certainly is the problem, and you really need to undo the damage.  Ideally, restore the database from a backup you took before running the SQL.  If you have no backup or don't want to do it, the next best option is to stop Jira, run SQL that reverses your changes, restart it and re-index.  If you can't do that either, then restart Jira, run a full re-index and just live in hope no permanent damage has been done.

And whatever you do as a repair, please throw away your SQL and never try it again.

[zaharovvv_suek_ru]

Thanks for your reply, Nic! I've stopped the job. 
Nic, Please, see my question
https://community.atlassian.com/t5/Jira-questions/Edit-linked-issue-if-main-issue-is-edited/qaq-p/859768

Thanks a lot, Nic!