Loading...

XML

Word

Printable

Details

Type: Suggestion
Resolution: Won't Do
Fix Version/s: None
Component/s: Project Administration - Versions
Labels:
- affects-cloud
- affects-server
- jw-fusion
- jw-platform
- sic
- sic-extend
- sic-scheme
- usability

Support reference count:
8
Current Status:
Hide

20th December 2017

Hi all,

Thanks for providing your thoughts and votes on this suggestion. I know it's been a while since we last commented on this suggestion and we are sorry to have kept you so long without a clear answer.

We (the Jira Server team) have recently reviewed this suggestion and how it would fit alongside our strategy and other customer priorities. I am afraid we are not planning to invest in creating versions on multiple projects.

While we absolutely understand the logic behind this request, we strongly believe that we should focus on making Jira simpler and easier to use rather then introduce additional complexity on both conceptual and technical level.

Jira as a tool promotes agile approach to project management, where simplicity is key and teams work iteravely to deliver small sections of a project at a time. We strongly believe that current version managment supports this approach.

Meanwhile, as Atlassian, we understand that growing teams may require more flexibility. This is why we are investing in Portfolio for Jira were cross-project releases are used to manage joint releases, dates, and milestones across multiple individual projects.

When you create a cross-project release and commit it to Jira Software, the release will be transformed into a regular release in each of the Jira projects that are part of the cross-project release. Issues assigned to the cross-project release in Portfolio will be assigned to the respective project-specific release in the issue's Jira Software project.

Also there are commercial third party apps which address similar use cases:

"Version Sync for JIRA" available for Server deployments. Please also check its sibling "Component Sync for JIRA".

"Releasedog" available for Server deployment.

Since investing in creating versions on multiple projects in the Jira Server is not aligned with our strategy and roadmap, we will be closing this issue. I understand that our decision may be disappointing, but we also hope that you will appreciate our candid and transparent approach. You can learn more about our approach to highly voted Server suggestions here.

Please don't hesitate to contact me if you have any questions.

Regards,
Gosia Kowalska
Senior Product Manager, Jira Server
Show
20th December 2017 Hi all, Thanks for providing your thoughts and votes on this suggestion. I know it's been a while since we last commented on this suggestion and we are sorry to have kept you so long without a clear answer. We (the Jira Server team) have recently reviewed this suggestion and how it would fit alongside our strategy and other customer priorities. I am afraid we are not planning to invest in creating versions on multiple projects. While we absolutely understand the logic behind this request, we strongly believe that we should focus on making Jira simpler and easier to use rather then introduce additional complexity on both conceptual and technical level. Jira as a tool promotes agile approach to project management, where simplicity is key and teams work iteravely to deliver small sections of a project at a time. We strongly believe that current version managment supports this approach. Meanwhile, as Atlassian, we understand that growing teams may require more flexibility. This is why we are investing in Portfolio for Jira were cross-project releases are used to manage joint releases, dates, and milestones across multiple individual projects. When you create a cross-project release and commit it to Jira Software, the release will be transformed into a regular release in each of the Jira projects that are part of the cross-project release. Issues assigned to the cross-project release in Portfolio will be assigned to the respective project-specific release in the issue's Jira Software project. Also there are commercial third party apps which address similar use cases: "Version Sync for JIRA" available for Server deployments. Please also check its sibling "Component Sync for JIRA" . "Releasedog" available for Server deployment. Since investing in creating versions on multiple projects in the Jira Server is not aligned with our strategy and roadmap, we will be closing this issue. I understand that our decision may be disappointing, but we also hope that you will appreciate our candid and transparent approach. You can learn more about our approach to highly voted Server suggestions here . Please don't hesitate to contact me if you have any questions. Regards, Gosia Kowalska Senior Product Manager, Jira Server
Feedback Policy:

We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

Description

NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

Original request description:

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.

Attachments

Issue Links

is duplicated by

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

Closed

JRASERVER-1140 Versions that Cross Projects

Closed

JRASERVER-1538 Filter on Versions and Components across Projects

Closed

JRASERVER-7120 Sharing Release-Version between Projects

Closed

JRASERVER-7527 XPlanner-style iteration management / planning / progress reports

Closed

JRASERVER-10380 Option to use same Version values across specified projects

Closed

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

Closed

JRASERVER-14569 Implement Component and Version Schemes

Closed

JRASERVER-16181 Enterprise/Global versioning across projects

Closed

JRASERVER-24350 We would like to assign the same Fixed Version across multiple projects

Closed

JSWSERVER-10058 Share the Version among several projects

Closed

JSWSERVER-14837 Iterations

Closed

JRASERVER-14588 Implement Component and Version Schemes

Gathering Interest

is incorporated by

JRASERVER-12241 Support for Product Suites / Sub-Projects

Closed

is related to

JRACLOUD-64868 Make Versions' fields accessible for JQL filtering

Closed

JRASERVER-8251 Filter on Version information accross Projects

Closed

JRASERVER-24232 Global Variables

Closed

JRASERVER-5884 Linking Version over projects

Gathering Interest

JRASERVER-47706 Categorize Components with the Same Name from Different Projects as One

Gathering Interest

JSWSERVER-9237 Multiple versions in version report

Gathering Interest

relates to

JRACLOUD-2698 Create versions on multiple projects

Closed

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

Closed

JRASERVER-27202 Global Fix Version field would be nice to have

Closed

JSWSERVER-663 As a GH user I would like my Planning Board to display multiple projects at once

Closed

JSWSERVER-705 As a GH user I would like my Task Board to display multiple projects at once

Closed

JSWSERVER-1800 Support multiple projects within GreenHopper

Closed

JRACLOUD-66760 Ability to pick Version from another Project

Gathering Interest

JSWSERVER-21107 Ability to pick Version from another Project

Gathering Interest

JSWSERVER-21289 Ability to pick Version from another Project

Gathering Interest

was cloned as

JRASERVER-71913 Order by version name (not ID)

Gathering Interest

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Wiki Page Loading...; Wiki Page Loading...

(8 is duplicated by, 1 is incorporated by, 6 is related to, 9 relates to, 1 was cloned as, 23 mentioned in)

Activity

People

Assignee:: Unassigned

Reporter:: Henri Yandell

Votes:: 788 Vote for this issue

Watchers:: 422 Start watching this issue

Dates

Created:: 18/Nov/2003 5:14 PM

Updated:: 23/Mar/2022 7:32 PM

Resolved:: 20/Dec/2017 2:34 PM