Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-19614

Roadmap feature for JIRA Server

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • AgileBoard
    • None
    • 22
    • 16
    • Hide

      As of today, the roadmaps feature is only available for the next-gen project type in Jira Software Cloud. We do not have plans to bring the roadmaps feature or next-gen project type from Jira Cloud to Jira Server or Jira Data Center.

      Atlassian's Cloud and Self-hosted product offerings are developed independently, which allows us to make the best prioritization decisions for each set of customers. For the self-hosted versions of Jira, this meant taking a different approach involving supporting more advanced planning, cross-project dependency management, capacity planning and global releases. All of which require a specialized tool - Portfolio for Jira Server and Data Center.

      While we are not committed to building out new roadmapping capabilities directly within Jira Server or Data Center, our team is working closely with the Portfolio for Jira team to improve the overlapping functionality of these offerings.

      That said, we strongly encourage you to check out our latest Portfolio for Jira Server and Data Center 3.0 platform release. In it, we have completely reimagined Portfolio to make it more simple and intuitive to use, flexible to your planning style and process, and transparent for all users. We think you'll like what you see.

      Alternatively, we suggest you to check out the Atlassian Marketplace for other solutions to meet your needs.

      To learn more about our recent investments in Jira Server and Data Center, please check out our dashboards showing Recently resolved issues and Current work and future plans.

      Best regards,
      The Jira Server and Data Center Team

      Show
      As of today, the roadmaps feature is only available for the next-gen project type in Jira Software Cloud. We do not have plans to bring the roadmaps feature or next-gen project type from Jira Cloud to Jira Server or Jira Data Center. Atlassian's Cloud and Self-hosted product offerings are developed independently, which allows us to make the best prioritization decisions for each set of customers. For the self-hosted versions of Jira, this meant taking a different approach involving supporting more advanced planning, cross-project dependency management, capacity planning and global releases. All of which require a specialized tool - Portfolio for Jira Server and Data Center. While we are not committed to building out new roadmapping capabilities directly within Jira Server or Data Center, our team is working closely with the Portfolio for Jira team to improve the overlapping functionality of these offerings. That said, we strongly encourage you to check out our latest Portfolio for Jira Server and Data Center 3.0 platform release. In it, we have completely reimagined Portfolio to make it more simple and intuitive to use, flexible to your planning style and process, and transparent for all users. We think you'll like what you see. Alternatively, we suggest you to check out the Atlassian Marketplace for other solutions to meet your needs. To learn more about our recent investments in Jira Server and Data Center, please check out our dashboards showing Recently resolved issues and Current work and future plans . Best regards, The Jira Server and Data Center Team
    • 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.

      Problem Definition

      At the moment, Roadmap funtionality is only available in JIRA Cloud
      Roadmap

      This is useful to manage a larger piece of task (Epic).

      Suggested Solution

      It would be great to have this available in JIRA Server as well to allow users to manage Epics better.

       

      See the following related community post: https://community.atlassian.com/t5/Next-gen-questions/When-does-JIRA-sofware-get-the-next-gen-road-map/qaq-p/927366

          Form Name

            [JSWSERVER-19614] Roadmap feature for JIRA Server

            Petr Plenkov added a comment -

            Hi! Actually just found out that is already available for more than 1 year with this release: https://confluence.atlassian.com/jirasoftware/jira-software-8-20-x-release-notes-1086411771.html

            Probably ticket needs to be updated

            Petr Plenkov added a comment - Hi! Actually just found out that is already available for more than 1 year with this release: https://confluence.atlassian.com/jirasoftware/jira-software-8-20-x-release-notes-1086411771.html Probably ticket needs to be updated

            bjoace added a comment -

            Our company started using bigGantt around a year ago and for me as nom-PM it works OK.

            https://en.wikipedia.org/wiki/BigGantt 

            bjoace added a comment - Our company started using bigGantt around a year ago and for me as nom-PM it works OK. https://en.wikipedia.org/wiki/BigGantt  

            Shilpa Nicodemus added a comment -

            Thanks @attila!  I'll take a look

            Shilpa Nicodemus added a comment - Thanks @attila!  I'll take a look

            Attila Bordás _Everit_ added a comment -

            @Shilpa Nicodemus You can also give this app a chance: https://marketplace.atlassian.com/apps/1220785/epic-roadmap-for-jira-software?hosting=datacenter&tab=overview

            Attila Bordás _Everit_ added a comment - @Shilpa Nicodemus You can also give this app a chance: https://marketplace.atlassian.com/apps/1220785/epic-roadmap-for-jira-software?hosting=datacenter&tab=overview

            Shilpa Nicodemus added a comment -

            Here are my notes.  I hesitate to be so transparent on my evaluation, so take it with a grain of salt that I had to evaluate fairly quickly (only spent a few hours each testing out the first two) and the requirements are very specific to my org.  

            Tool Type Decision Comment
            BigPicture Jira Plugin rejected Any roadmapping plugin/integration we choose, we should be able to train the sr managers and directors to use.  This tool would be difficult.  It’s over-engineered, and the UI isn’t intuitive.  Self-service enablement and support would be highly taxing on a few knowledgeable SMEs, and adoption would be lethargic at best.  Even if a one-time setup to make it work seamlessly for everyone was possible, it’s frankly just not visually appealing enough to justify it the effort.  That’s a requirement, because we’d likely be screenshotting roadmaps for leadership decks or sending links directly to leaders.
            Easy Agile Roadmaps for Jira Jira Plugin rejected
            • Requires pulling start and end date fields from the original tickets
            • Visualize Epic progress
              • This is not usable.  The epic progress bar is based on the % of estimated work that has been completed, and NOT the status of the ticket itself being open, in progress or done.  Epic Progress/Statistics (easyagile.com).  Most of our teams don't do story points or estimation at this level of maturity. 
            • It doesn't automatically pull in Fix Version
            Structure.Gantt Jira Plugin   Requires another plugin, Structure for Jira.  Looks complicated.
            Aha! roadmaps for Jira Jira Plugin   This looks too complicated.
            Agile User Story Map & Product Roadmap for Jira Jira Plugin haven't assessed yet  

            Shilpa Nicodemus added a comment - Here are my notes.  I hesitate to be so transparent on my evaluation, so take it with a grain of salt that I had to evaluate fairly quickly (only spent a few hours each testing out the first two) and the requirements are very specific to my org.   Tool Type Decision Comment BigPicture Jira Plugin rejected Any roadmapping plugin/integration we choose, we should be able to train the sr managers and directors to use.  This tool would be difficult.  It’s over-engineered, and the UI isn’t intuitive.  Self-service enablement and support would be highly taxing on a few knowledgeable SMEs, and adoption would be lethargic at best.  Even if a one-time setup to make it work seamlessly for everyone was possible, it’s frankly just not visually appealing enough to justify it the effort.  That’s a requirement, because we’d likely be screenshotting roadmaps for leadership decks or sending links directly to leaders. Easy Agile Roadmaps for Jira Jira Plugin rejected Requires pulling start and end date fields from the original tickets I didn't have admin access over the tool, so I have to assume you can specify exactly which date fields you need. You can see it in the help files. Syncing Jira Date Fields (easyagile.com) Visualize Epic progress This is not usable.  The epic progress bar is based on the % of estimated work that has been completed, and NOT the status of the ticket itself being open, in progress or done.   Epic Progress/Statistics (easyagile.com) .  Most of our teams don't do story points or estimation at this level of maturity.  It doesn't automatically pull in Fix Version Structure.Gantt Jira Plugin   Requires another plugin, Structure for Jira.  Looks complicated. Aha! roadmaps for Jira Jira Plugin   This looks too complicated. Agile User Story Map & Product Roadmap for Jira Jira Plugin haven't assessed yet  

            Georgia Compton added a comment -

            96f1f9119d82 did you ever look into any plugins? If you have any suggestions or user feedback on these please share  

            Georgia Compton added a comment - 96f1f9119d82 did you ever look into any plugins? If you have any suggestions or user feedback on these please share  

            Joyce A added a comment -

            We have Structure.Gantt. Structure.Gantt requires the full Structure plugin to be installed as well.   We already had the Structure plug-in installed.  Structure is one of our most used and loved plug-ins.

            It was a real plus adding Structure.Gantt for project and resource management .  It has better resource management than Advanced Roadmaps.  We discontinued our Advanced Roadmap licenses because we could do so much more with Structure.Gantt.

            Joyce A added a comment - We have Structure.Gantt. Structure.Gantt requires the full Structure plugin to be installed as well.   We already had the Structure plug-in installed.  Structure is one of our most used and loved plug-ins. It was a real plus adding Structure.Gantt for project and resource management .  It has better resource management than Advanced Roadmaps.  We discontinued our Advanced Roadmap licenses because we could do so much more with Structure.Gantt.

            Shilpa Nicodemus added a comment -

            At this point, I'm just going to go in the direction of using a plugin.  Does anyone use any of these? 

            • [Easy Agile Roadmaps for Jira | Atlassian Marketplace|https://marketplace.atlassian.com/apps/1215695/easy-agile-roadmaps-for-jira?hosting=server&tab=overview]
            • [Agile User Story Map & Product Roadmap for Jira | Atlassian Marketplace|https://marketplace.atlassian.com/apps/1222309/agile-user-story-map-product-roadmap-for-jira?hosting=server&tab=overview]
            • [Aha! roadmaps for Jira | Atlassian Marketplace|https://marketplace.atlassian.com/apps/1211698/aha-roadmaps-for-jira?hosting=server&tab=overview]
            • [Structure.Gantt - Planning at Scale | Atlassian Marketplace|https://marketplace.atlassian.com/apps/1217809/structure-gantt-planning-at-scale?hosting=server&tab=overview]
            • Something else?

            Shilpa Nicodemus added a comment - At this point, I'm just going to go in the direction of using a plugin.  Does anyone use any of these?  [Easy Agile Roadmaps for Jira | Atlassian Marketplace|https://marketplace.atlassian.com/apps/1215695/easy-agile-roadmaps-for-jira?hosting=server&tab=overview] [Agile User Story Map & Product Roadmap for Jira | Atlassian Marketplace|https://marketplace.atlassian.com/apps/1222309/agile-user-story-map-product-roadmap-for-jira?hosting=server&tab=overview] [Aha! roadmaps for Jira | Atlassian Marketplace|https://marketplace.atlassian.com/apps/1211698/aha-roadmaps-for-jira?hosting=server&tab=overview] [Structure.Gantt - Planning at Scale | Atlassian Marketplace|https://marketplace.atlassian.com/apps/1217809/structure-gantt-planning-at-scale?hosting=server&tab=overview] Something else?

            Russell Siachico added a comment -

            +1

            Russell Siachico added a comment - +1

            Timo Theunkens added a comment -

            @Brian Hair, which is understandable, however the cost for datacenter is still double the cost of the server instance. They cut costs by discontinuing support on an entire branch and force people to migrate to datacenter at a higher cost while they won't use most of the advantages for datacenter which are mostly to support high availability. But you are right for us the datacenter would be a possibility, but since the cost doubles we wouldn't be able to purchase this within our framework contract due to government laws on acquisition and fair competition. so we need to go back on the market and allow all company's who subscribe to the gunning to compete for the contract, and I'm sure that Atlassian hasn't got such a good chance of winning at there current pricing at this point.

             

            @Mark Dorsi, there are numerous reasons, the main reasons for us are less control about data security since we are a public service, dependability on internet instead of intranet, vendor lock-in, limited integration, extra steps in troubleshooting by external companies, no guaranty on a good support level, bigger chance to be hacked since cloud providers are interesting targets, higher recurrent costs, no control on reliability, no internal knowledge building ...

            Above issues are the reason why we do not allow any cloud based SaaS solutions as a rule in our company unless there is no other alternative. 

            Timo Theunkens added a comment - @Brian Hair, which is understandable, however the cost for datacenter is still double the cost of the server instance. They cut costs by discontinuing support on an entire branch and force people to migrate to datacenter at a higher cost while they won't use most of the advantages for datacenter which are mostly to support high availability. But you are right for us the datacenter would be a possibility, but since the cost doubles we wouldn't be able to purchase this within our framework contract due to government laws on acquisition and fair competition. so we need to go back on the market and allow all company's who subscribe to the gunning to compete for the contract, and I'm sure that Atlassian hasn't got such a good chance of winning at there current pricing at this point.   @Mark Dorsi, there are numerous reasons, the main reasons for us are less control about data security since we are a public service, dependability on internet instead of intranet, vendor lock-in, limited integration, extra steps in troubleshooting by external companies, no guaranty on a good support level, bigger chance to be hacked since cloud providers are interesting targets, higher recurrent costs, no control on reliability, no internal knowledge building ... Above issues are the reason why we do not allow any cloud based SaaS solutions as a rule in our company unless there is no other alternative. 

              Unassigned Unassigned
              azuhra Aqqiela
              Votes:
              807 Vote for this issue
              Watchers:
              382 Start watching this issue

                Created:
                Updated: