issue status in release is not freezed

[cyrille_guillard]

I am wondering if there is a way to keep the issue inside a release at the status it has when the release was closed.

Scenario:

Create a release

Add issue 1 when in status Open

Close the release

change issue 1 state to done

Open the release

=> should see the issue 1 in the state it was when  the release was close.

I understand it may appear weird, but it is essential to keep track of history of what is done.

In my company we have states  like 'Postpone' or 'Deviation', and we are looking for a way to keep track of these not final state which are final at the release time. So that we can report this release was done with following 'deviation's' issues...(and keep track of that)

It sounds like jira is not appropriate for that, but I prefer to ask maybe there is a way to do it.

[Aron Gombas _Midori_]

The PDF Automation app provides an automation action called Attach PDF which generates PDF documents from the passed issues and attaches it to an arbitrary issue.

In your case, you could create a PDF snapshot of each issue in the release, and attach it to the originating issue itself. If you used a naming convention like "${issue.key}-${release.name}.pdf" or something, it could be very intuitive and simple.

For example, in this screenshot, we create daily snapshots where the name encodes the date:

[Matteo Gubellini _SoftComply_]

Hi @cyrille_guillard ,

We have an App that does something like this, but it is for Confluence.

It basically freezes the content of a Jira report in a page. I'm not sure this is exactly what you are looking for, nevertheless the link is below.

https://marketplace.atlassian.com/apps/1224834/softcomply-static-snapshots-to-freeze-confluence-pages?hosting=cloud&tab=overview

Matteo

[Matteo Gubellini _SoftComply_]

Also please check this blog post:

https://softcomply.com/how-to-maintain-a-documentation-baseline-in-confluence/

Matteo

[Rina Nir]

@cyrille_guillard 

I suggest you check out the App Jira Snapshots for Confluence. It captures Jira data at a point in time, and was designed specifically to use cases like yours. It's a Confluence app- in case you are not using Confluence yet, you might launch a free Confluence site to take advantage of this App.

Disclosure: I am the product manager of the App and the CEO of RadBee.

I hope this helps,

Rina

[cyrille_guillard]

@Rina Nirwe have a few licenses of Confluence, but not using it heavily. I will give a look at that functionality. Thanks for the suggestion.

[Trudy Claspill]

Hello @cyrille_guillard 

What you are trying to do is not possible with the native Jira functionality. When you view a Release in Jira, you will see the current Status of the issues in that Release.

If the work for the issue is not completed when the Release is closed, I would recommend that you pull it out of the Release (remove that version from the Fix Version/s field). Maybe you should instead records that Release in an Affected Version/s field to indicate it was not resolved in a particular release.

[cyrille_guillard]

Ok thanks to confirm what I have seen.

Unfortunately, no the status is an end status at the time of the release is close (it a sort of temporary solution). And we need to keep track that the particular ticket at that release was in that 'deviated' state (release was accepted event if the ticket was not solved).

In my understanding, the usage of the release we are trying to do is not product release version standard use.

We were hopping to use release for something that is more like a snapshot of the project quality, for a particular product release... a bit weird I admit... excel may do the trick.