Uploaded image for project: 'JIRA Server (including JIRA Core)'
  1. JIRA Server (including JIRA Core)
  2. JRASERVER-2698

Create versions on multiple projects

    XMLWordPrintable

    Details

    • 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 An updated workflow for server feature suggestions.
    • 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:

      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

      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

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                bayard Henri Yandell
              • Votes:
                788 Vote for this issue
                Watchers:
                412 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: