Issue Type "Release" or "Delivery" for planning Releases?

[Ulrike Engel]

Hi all!

I am currently looking for a solution to plan Releases in a JIRA Project for a product that multiple teams work on.

The following aspects should be considered:

• Around 25 Teams work on their area of responsibility (mainly a System/Component) and map their Tasks, User Stories and Defects/Fixes to their upcoming System Releases
• Release Cycles are not synchronized, each team has its own Release Schedule (some every 2 Weeks, some every 3 Month)
• Besides the information which User Stories, Tasks and Defects/Fixes are planned to be part of a Release; additional information on the Release itself should be visible - e.g. the planned dates for Deployments in Test Environment and Production Environment. 
• Creation of Views like "Show All Releases that are planned to be deployed to Test Environment in CW23" should be possible 

From my understanding, there´s no way to add additional information to the "Fix Version", which is why we are currently thinking about creating an Issue Type "Release" or "Delivery" with all the Information/fields we want to track.

The Issues that are planned to be part of the release then would be linked to it, e.g. using "is realized by ...". 

For Visualization purposes, Structure and Structure.gantt look good to us.  

Does anyone have experience with that kind of approach? 

Any opinions on advantages, disadvantages or alternative Solutions would be helpful.

[madhu_tejas]

@Ulrike Engel Hello Ulrike, Did you find any similar solution ?