any chances to get this implemented?

Version report is one of best reports and it works great with one project for many teams setup that was typical in 2010 Today we setup one project for one team thanks to schemas. But I didn't find solution for Version report to get more than one version

The lack of being able to do this is impacting our teams in the following ways:

• We have to create 2 tickets for each of the projects that are worked on by the same team
• We have to create 2 tickets for our QA teams - One in the QA project that uses Zephyr and the other in the development project. 

This is an enormous amount of additional work. Please, please provide this functionality soon!

I cannot agree with you more Bhuwanesh - really disappointing.

This is never going to get fixed... It's pointless to even pursue this now.

This issue was raised in 2013 - and not even an update from the Jira team?

A much-needed feature for us. Any plan for this? Our teams are working on multiple projects that are part of the same release from the business point of view. This would be a really helpful feature.

This would be very powerful and save a tone of manual work.

any news on this feature Jira folks?

My team has also been very interested in seeing this feature rolled out as it would allow us to see across various projects when their combined predicted completion date would be. We have various teams working on a project in the same program increment (PI) and want to get a sense of when the PI will finish in one single chart. 

Hi there! Any news on this feature yet? 

Any news on this one Jira Team?

We use Jira heavily for multiple purposes, and this is one of the biggest roadblocks we have at the moment. We need to be able to have overall reports that embrace multiple projects.

For instance, from an ITSM perspective, one of our reports is around CSAT, and each project (regions) has its own CSAT report. At the moment, there is no way we can create a report that embraces multiple projects. We really need this and ASAP.

Lars, is there any chance you can let us know whether is possible to make this functionality a reality and when we can expect this?

Much appreciated,

Juan Alvarez, Customer Success Director at Squiz Australia

At the moment we create a version for every milestone in a project. We want the versions linked together, or linked to 1 big MVP version.

And after we release (we release every sprint) we tag the actual release version (ex. 1.15.0)

We could create versions for every milestone and a version for the MVP. But you can only show one version in the backlog  So that's not an option. 

We want an complete overview of our coming milestones, with release dates (like in the VersionReport, but then for multiple versions.)

I also would be interested in this kind of feature 

We recently introduced Jira here at work.

One of the project teams is struggling with the same as stated here: they filled in the backlog and dividied the stories over several releases. However, they started working on multiple releases in parallel.

For each release they can see the version report, but their question is whether it is possible to see one report over multiple (all) releases.

Just to add my comment, we have an Enterprise Portfolio Management Office that is basically asking for a dashboard view over multiple projects in the one view.  Please see attached image for your information.  

As it stands, the Version Report and Release Burndown force you to put all stories into one project so that one version can cover them all. This is not feasible for larger organizations such as ours, where multiple projects are needed for project admin purposes.

The other reports have no problem with the fact that stories are from different projects. Epics can even be in different projects from their stories.

But not having version reports that cover all the versions means, for example, that you have no way to see the big picture for, say, a program increment (using SAFE-speak now).

What would it take to have a good discussion with Atlassian about this missing feature?

I would like to simply be able to create a chart just like the Version Report, but which includes a user-defined selection of versions from within that project.

This chart is invaluable for showing management the impact of scope creep as the total work line keeps rising. I would love to be able to say "since the start of the project, this is our progress on all tasks, and this is the creep in requirements across the whole project".

rzo, please Vote and Watch this issue instead – https://jira.atlassian.com/browse/JRA-14588

This is related to the linked question on Atlassian Answers.

We would appreciate if we could span versions across various JIRA projects and run overall versions reports on them. This is especially important on enterprise setups with multiple projects affecting multiple applications and vice versa.

I would like to add explicitly specific requirement to this suggestion. It might be well covered by the implementation based on a filter/jql mechanism, but just in case You are not going this way.

• it is possible to see version report for multiple versions coming from multiple projects.
  This can be achieved by multiselection of version or by In case version name is matching between project displayed as new entries in combobox as ie (CrossProjectVersion: <VersionName>)
  Looking at some comments on a doc page I am not only one in need for that.
  https://confluence.atlassian.com/display/AGILE/Viewing+the+Version+Report?focusedCommentId=701433646&#comment-701433646

I just created and linked in GHS-9645 since I wanted to elevate up to the summary of an issue/story the desire to get more control over the set of stories/issues that are included in a version report. While including multiple versions is absolutely something I would want to do to look at longer term planning, I also would want to be able to temporarily exclude remaining low priority stories and see how that might affect the projected release date (or potentially apply other filters as well).

I created this since I could. Is this a good way of suggesting features?