Releasing version always says unresolved issue

[aaronhoffman]

Hello,

Whenever we release a new version via JIRA Cloud we see a popup and at the top it says "This release contains X unresolved issue"

However when we go into the release a see the issues list we can confirm that ALL issues show "RESOLVED". 

How can we fix this?

Thanks in advance

[Dominik Ras]

@aaronhoffman I think you might be mixing STATUS or status category and RESOLUTION ✋🛑 


Those are not the same - not synonyms. If you intend to mark a version as released, JIRA wants included issues to be marked as resolved, not only DONE (status category). Notice the field right next to STATUS on my screenshot:  

I feel your pain 😩 and this how I deal with it: I set up automation to kick in after I release a version: that automation changes items' status to RELEASED (particular custom status in my workflow - it doesn't have to do that in your JIRA) and I also set resolution to DONE. So When I click the release button and get the prompt complaining about unresoled item, I choose to ignore that, because I know that in a minute or two automation will handle that for me.

Sample basic automation flow for that:

 

[Gip]

Hi @aaronhoffman - This may be due to sub-tasks which have been created against those issues still being open. The issues in the release version may not show your sub-tasks if the team members have not set the fix version on the sub-task as well as it is not automatically inherited from the parent ticket.

[aaronhoffman]

Hi @Gip , thanks for your reply. In this case, I checked and can confirm that there are no sub-tasks. Just today I ran a test using only 1 issue under a given release and no sub-tasks and still ran into the same message "This release contains 1 unresolved issue".

[Gip]

Hi @aaronhoffman - Ah interesting, the only other thing I could think of without knowing the full setup of your Jira project is that there is an issue with the Jira workflow for those issues. It may have been setup with a status that is not considered "resolved" by Jira even though the status name that has been set against may infer it.