When an issue (Task | Story | Defect) has multiple Fix Versions, then how it impacts Version Report

[Ashish Gupta]

Many a times we come across a scenario when a User Story or lets say a Task, have multiple Fix Versions.

Let's say, we have a User Story of 5 Story points. This Story was planned in Release 2.0. Somehow, it spilled over to next Release which is 2.1.

In such cases, we usually keep both the Releases in the Fix Version of the User Story. Now in this case, how the "Version Report" graph for Release 2.0 or 2.1 is generated or impacted corresponding to this User Story. 

Story Point (5) of this User Story will be accounted in Version Report of Release 2.0 or Release 2.1 or both?

[Tarun Sapra]

Hello @Ashish Gupta 

"In such cases, we usually keep both the Releases in the Fix Version of the User Story. Now in this case, how the "Version Report" graph for Release 2.0 or 2.1 is generated or impacted corresponding to this User Story. "

I don't think that's a good practice to keep the story mapped to an version which was released (2.0) , while the story is released is 2.1.

You can easily bulk-update the stories to reflect the correct version. And if you still have a story which has two fixVersion then the same story will appear in the version report of both versions.

Also, since fixVersion supports "Was" operator you can easily use the history search to find issues whose fixVersion was changed to a new one. 

[Ashish Gupta]

Hi @Tarun Sapra  -

Thanks for responding.

I agree with your point that it is not a good practice to keep the Story or a Task mapped to multiple versions. But sometimes, based on the customer need you have to do this. Another example, let's say a "Defect" which was put in the Backlog at the time of its submission. Now the defect has be fixed in multiple releases. So, in such cases we have to map multiple releases for the Defect.