[#JRA-2698] Create versions on multiple projects

JIRA

Create versions on multiple projects

Created: 18/Nov/03 11:14 AM Updated: Thursday 06:11 AM

Component/s:

Project Management

Affects Version/s:

2.5.1 Professional

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Duplicate

This issue is duplicated by:

~~JRA-10650~~ Issue navigator isn't sorting correctly if search-result contains entries from more than 1 project

~~JRA-7527~~ XPlanner-style iteration management / planning / progress reports

~~JRA-16702~~ Iterations

~~JRA-7120~~ Sharing Release-Version between Projects

~~JRA-1140~~ Versions that Cross Projects

~~JRA-16181~~ Enterprise/Global versioning across projects

~~JRA-10380~~ Option to use same Version values across specified projects

~~JRA-12341~~ Ability to share components and versions list between several projects

~~JRA-14569~~ Implement Component and Version Schemes

Part

This issue is incorporated by:

JRA-12241 Support for Product Suites / Sub-Projects

Reference

This issue relates to:

JRA-8758 Cannot create filter for multiple projects all issues in version "Released Versions"

This issue is related to:

JRA-5884 Linking Version over projects

~~JRA-8251~~ Filter on Version information accross Projects

Participants:	Christoph Ebner von Eschenbach, Dennis Mendelson, Florian Ortner, Gunnar Wagenknecht, Henri Yandell, jboyle, John Price, Jordan Dea-Mattson and Stephan Lagraulet
Since last comment:	41 weeks, 2 days ago
Labels:
Support reference count:	8

Description

« Hide

In my work's instance of JIRA we have multiple products that usually get released as a part of a larger project. It would be a lot nicer if we had a way to edit multiple projects at the same time, mainly to add new versions, release the version.

Would also be nice if JIRA knew those versions were the same, apart from the same name, so a report could be created on it etc.

All

Comments

Work Log

Change History

Sort Order:

[ Permalink | « Hide ]

Stephan Lagraulet added a comment - 24/Oct/06 07:34 AM

It would be great to have this feature.
This is considered critical for the managers in my company.

[ Permalink | « Hide ]

Dennis Mendelson added a comment - 11/Jan/07 04:34 AM

An alternative way to solve this problem is surely to enable filters to match all Jiras in a specified set of project/release pairs. That way, if a given production turnover will include the disting of project A, release x, and project B, release y, it would be simple to create a filter (and thus a report) that lets one track during the development cycle all relevant issues.

[ Permalink | « Hide ]

jboyle added a comment - 16/Nov/07 01:04 PM

In my case, we use 'projects' on a per-customer basis. Therefore, each version release will have items for different customers and general bugfixes - creating, managing versions across all the projects is very time-consuming. A "global version" vs "project-specific version" methodology would be desirable for us.

[ Permalink | « Hide ]

Florian Ortner added a comment - 15/Feb/08 05:10 AM

As an ISV type of company we have to create/maintain our main product's version across almost all projects ==> this feature would be helpful and simplify administration.

[ Permalink | « Hide ]

Gunnar Wagenknecht added a comment - 18/Apr/08 09:38 AM

~~JRA-10380~~ looks like another dup of this one. Any news on the issue? We would also like to have this ability in JIRA.

[ Permalink | « Hide ]

John Price added a comment - 21/Apr/08 03:58 PM

This would help us as well. I am at a company that does hosted (Software as a Service) apps. Our process works like this:

we have JIRA projects for each major product area (higher level than components).
about 6 of the projects share release cycles, so that updates all get released at once.
I need a way to give all 6 projects the same versions and easily do reports etc. across projects.

[ Permalink | « Hide ]

Christoph Ebner von Eschenbach added a comment - 11/Jul/08 08:21 AM

We would also like to have this feature implemented.

We use an "external open" project for the communication with our customers and an internal one to keep the internal "techie-talk" and the technical details apart from the customer.

Till now there's no possibility to include the issues from both (or several) projects within one version for planning and management.

[ Permalink | « Hide ]

Jordan Dea-Mattson added a comment - 18/Sep/08 01:31 PM

We have multiple projects which represent separate products and which logically belong at the Project vs. Component level. These projects are released by and large on synchronized schedules.

Currently, I am forced to create and manage versions across these projects. Having the ability to share versions across Projects would be extremely helpful.

[ Permalink | « Hide ]

Henri Yandell added a comment - 18/Sep/08 02:30 PM

One thing to note is the ability for the quick search to find versions across projects.

—
Issues with a particular Version
You can use the prefix "v:" to search for issues with a particular version(s). Note that there
can be no spaces between "v:" and the version name. "v:3.0" will match against the following
versions (for example):
• 3.0
• 3.0 enterprise
• 3.0 standard
but will not match against the following versions (for example):
• 3.0.1
• 3.0.0.4
That is, it will match against any version that contains the string you specify followed
immediately by a space, but not against versions that do not contain a space immediately after
the string you specify.
Issues with a particular Fix For Version
You can use the prefix "ff:" to search for issues with a particular fix for version(s).
The search mechanism is the same as the quick search for Issues with a particular
Version.
—