New and Improved 3.13 Beta. Highlights: Shareable filters and dashboards and lots of other goodies. Any feedback can be raised as JIRA issues in the JIRA project.
Issue Details (XML | Word | Printable)

Key: JRA-2698
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Henri Yandell
Votes: 43
Watchers: 25
Operations

If you were logged in you would be able to see more operations.
JIRA

Create versions on multiple projects

Created: 18/Nov/03 11:14 AM   Updated: 11/Jul/08 08:21 AM
Component/s: Project Management
Affects Version/s: 2.5.1 Professional
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Duplicate
 
Part
 
Reference

Participants: Christoph Ebner von Eschenbach, Dennis Mendelson, Florian Ortner, Gunnar Wagenknecht, Henri Yandell, jboyle, John Price and Stephan Lagraulet
Since last comment: 5 weeks, 4 days ago
Support reference count: 6
Labels:


 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: Ascending order - Click to sort in descending order
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.

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.

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.

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.

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.

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.

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.