The purpose of this need is to give the ability to ease the management of the global planning activities, such as maintenance versus release planning, or the ability to plan a Sprint targeting delivering issues assigned to a major and a maintenance release at the same time.

For instance, let's consider the following Version Types:

• Major Release
• Maintenance Release
• Sprint

We can than have the following Fix Versions and their respective types:

As opposed to the Greenhopper plugin way of managing Releases dependencies, there is no parent-children relationship between these Fix Versions. For instance, it's not unrealistic to consider a given issue assigned at the SAME TIME to V2.12 for maintenance purposes, to V3.0 for back-porting reasons to the major release and to the Sprint 4 for the team planing purpose.

Having that is place, I clearly see multiple advantages:

1- The ability to filter by Release Type (All next maintenance releases content or current and next Sprints plans)

2- Given the first point, I would see a simple way to simplify the planning board right hand view given the ability to restrict the view selected release types only.

3- In the planning board again, the ability to reschedule issues between releases of the same type while keeping the other assignment unchanged: for instance changing the Maintenance Release of an issue doesn't change its Major release and its Sprint assignment.

Last but not least, it's an elegant way of solving GHS-945