How to deal with version to version releases

[Marie Bastin]

Hello,

I'm currently working on a project on Jira software where we just released version 1.1. We now want to start working on version 1.2 which will contain some new features and some improvements of already existing features. Most of features released in version 1.1 will remain unchanged and maintained in version 1.2.

The questions are the following:

- What are the good practices in Jira software to properly document issues that were released in one version and will be improved in the following version ? So far we tried to simply add the tag version 1.2 to the concerned issues and changed their status from "done" to "backlog", but this broke the version 1.1 reporting (warning that some issues from version 1.1 are not done yet).

- For the issues that will be maintained in the new version (without modification), is it enough to add the tag version 1.2 ? We also considered leaving those issues with only the tag version 1.1 and that all issues from version 1.1 will be implicitly part of version 1.2, but in that case, how do we document an issue from version 1.1 that we no longer wish to maintain in version 1.2 ?

Thanks in advance for your help !

[Bastian Stehmann · Accepted solution]

Hi @Marie Bastin

Welcome to the community. 

I would create new issues for the improvements you are doing in version 1.2 and add that Version to that issues. You can link them to the first issue they are related to show that connection. 

Then you can see exactly what you did in 1.1 and what you did in 1.2.

If you need a complete list of features that are in 1.2 you have to add all this issues to Version 1.2. Maybe it will make sense to create a new version custom field for this (i.e. included in version or something like that). Then you can query that field to find all relevant issues and it will not break your reports.

[Marie Bastin]

Hello @Bastian Stehmann

I will follow your advice,

Thanks for your answer !