Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-2698

Create versions on multiple projects

XMLWordPrintable

    • 8
    • 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
    • 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.

      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.

            [JRASERVER-2698] Create versions on multiple projects

            Max Foerster - Decadis AG added a comment -

            Hey everyone,

            since the need for this feature has remained high among all project and Jira administrators, we put in some effort and added cross-project bulk editing for

            • components
            • versions
            • users and roles

            to our app called Admin Toolbox for Jira in the latest release. You can now add, edit and remove a version from all projects you have access to in a central location. The same applies to components, users and roles, of course! 👍🏼 I wish you in advance happy holidays.

            Best, Max

            Max Foerster - Decadis AG added a comment - Hey everyone, since the need for this feature has remained high among all project and Jira administrators, we put in some effort and added cross-project bulk editing for components versions users and roles to our app called Admin Toolbox for Jira in the latest release. You can now add, edit and remove a version from all projects you have access to in a central location. The same applies to components, users and roles, of course! 👍🏼 I wish you in advance happy holidays. Best, Max

            Michal Ha added a comment -

            Hey Guys

            I also was investigating that, there is Jira automation plugin, now managed by atlassian.

            There is 'create version' option. They just need to enable multiple project picker like for other actons and will be available, I will try to raise that

            Michal Ha added a comment - Hey Guys I also was investigating that, there is Jira automation plugin, now managed by atlassian. There is 'create version' option. They just need to enable multiple project picker like for other actons and will be available, I will try to raise that

            Ricardo Gomes added a comment -

            Thanks, @Marcus.
            At least I let all my rage out

            I bet Atlassian has had their share of frustration from lots of users on this topic already in the past but that didn't seem to make any difference anyway... ¯_(ツ)_/¯

            Ricardo Gomes added a comment - Thanks, @Marcus. At least I let all my rage out I bet Atlassian has had their share of frustration from lots of users on this topic already in the past but that didn't seem to make any difference anyway... ¯_(ツ)_/¯

            Marcus added a comment -

            @Ricardo Gomes

            >> The ticket is already closed, so nobody from Atlassian will react to any comments here anymore.

            Marcus added a comment - @Ricardo Gomes >> The ticket is already closed, so nobody from Atlassian will react to any comments here anymore.

            Ricardo Gomes added a comment -

            Reusing Components and Fix Versions are the most common use case across multiple projects that there's on God's green earth. How do I have to get Portfolio just for a ridiculously obvious feature that should be in Jira??
            Sorry for commenting again on this insanity but I came across the need today again and have to explain to our executives (again) why we're paying almost 10k a month for Jira and can't share one field across multiple projects.

            Maybe Atlassian can have their CEO talk to my CEO and explain better than I can...??

            Ricardo Gomes added a comment - Reusing Components and Fix Versions are the most common use case across multiple projects that there's on God's green earth. How do I have to get Portfolio just for a ridiculously obvious feature that should be in Jira?? Sorry for commenting again on this insanity but I came across the need today again and have to explain to our executives (again) why we're paying almost 10k a month for Jira and can't share one field across multiple projects. Maybe Atlassian can have their CEO talk to my CEO and explain better than I can...??

            Mark Thompson added a comment -

            People want this so bad they are commenting on a ticket "resolved" in 2017.  It's good for one thing.  Ask me about Jira - First thing I do is send them to a ticket like this.  Enough said.

            Mark Thompson added a comment - People want this so bad they are commenting on a ticket "resolved" in 2017.  It's good for one thing.  Ask me about Jira - First thing I do is send them to a ticket like this.  Enough said.

            Ricardo Gomes added a comment -

            As per previous comment from Atlassian:

            "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."

            but then

            "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..."

            So "we will not invest in Jira" but "we will invest in Jira Portfolio" - so all users can pay for it. Ridiculous!

            It's important to remember the need for fix version across multiple projects was born in Jira and should be resolved there first. Creating another product to charge customers when you're actually covering gaps in a previous product is not a good practice, Atlassian... and I'll stop here.

            Ricardo Gomes added a comment - As per previous comment from Atlassian: "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." but then "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..." So "we will not invest in Jira" but "we will invest in Jira Portfolio" - so all users can pay for it. Ridiculous! It's important to remember the need for fix version across multiple projects was born in Jira and should be resolved there first. Creating another product to charge customers when you're actually covering gaps in a previous product is not a good practice, Atlassian... and I'll stop here.

            Ravi added a comment -

            Pathetic to see this request was marked with the *Resolution as "*Won't Do". Lot of challenges with Fix versions field

            1. Doesn't have sorting 
            2. As mentioned in the ticket, if the same version being managed in deterrent projects, entry has to populate in all the projects. 
            3.  If we want to mark the version as released, we have to it in all the projects.

             

            Ravi added a comment - Pathetic to see this request was marked with the *Resolution as "*Won't Do". Lot of challenges with Fix versions field Doesn't have sorting  As mentioned in the ticket, if the same version being managed in deterrent projects, entry has to populate in all the projects.   If we want to mark the version as released, we have to it in all the projects.  

            davecagle added a comment -

            @Derek Thrasher - We went with Version One.   It solved other issues we had related to portfolio management and planning that Jira fell short on.

            davecagle added a comment - @Derek Thrasher - We went with Version One.   It solved other issues we had related to portfolio management and planning that Jira fell short on.

            Derek Thrasher added a comment -

            @davecagle, what tool do you use now?

            Derek Thrasher added a comment - @davecagle, what tool do you use now?

              Unassigned Unassigned
              62501d1e54af Henri Yandell
              Votes:
              788 Vote for this issue
              Watchers:
              424 Start watching this issue

                Created:
                Updated:
                Resolved: