Loving it. Thanks.

Agree.

I echo people who would like to have the roadmap option in the Classic Business Projetcs!

I had sent a request to Jira about enabling in classic business projects but they told me it is only available in classic software and next gen software, so I set up my project as a classic software project. However, I also echo both Liam and Ashley in wanting this enabled for classic business project. 

I echo Liam's comment.  I do not see this feature available in Classic Business Projects.  Can you enable this for Business Projects as well?

@deniss - Is it available for Classic Business Projects too? I don't see it as an option in any settings, and Business Projects don't have 'Board settings'.

Thanks

Roadmaps are now out of Beta and will be enabled by default for all new Classic type projects 

Hi, @toni!

 You can try Advanced Roadmaps for Jira – https://marketplace.atlassian.com/apps/1212136/advanced-roadmaps-formerly-portfolio?hosting=server&tab=overview

This plugin allows you to work with cross-project releases.

Hi - I need to be able to manage releases across projects, and it looks like cross-project releases are only possible with a Next Gen project. I do not want to move to a Next Gen project bc I will lose other features. Anyone able to recommend an alternative to managing releases across multiple Jira projects?

Hello 4d73e5d04b96,

sorry to hear you are still unable to enable the roadmap for your board. The board needs to be located within a project and not a user to allow enabling the roadmap. It also needs to be based on a JQL that only pulls in issues from the project the board is located in. Another reason might be that you do not have admin permissions on the respective board or project - are you able to access to board setting? When you say "I don't have backlog or active sprints in my project type" - does this mean you are working with a Kanban board? I think it would be easiest for you to raise a support request on https://support.atlassian.com/contact/#/ so our support engineers can assist you.

Sorry again for the issues you are experiencing, I'm sure our support team will be able to help.
Kind regards,
Albert Kavelar | Jira Software

Hi Nitin, it still isn't working for me. Does the classic business project have to be a certain project type for it to work? I don't have backlog or active sprints in my project type... however I would still like to be able to use roadmaps. Please assist! Thanks  

Where can I create a ticket to get further assistance... I don't want to create one under nextgen cloud but business cloud. Thanks! 

Hi Team,

I have activated Roadmap Beta on my existing Classic project. When I switch to Roadmap view it shows Improvements not Epics in the first column. Can you please advice how to change the view? Thank you in advance!

SOLVED: I figured out the already estabilished project does not have EPIC issue type added to  issue type scheme, therefore Epics items were created as Improvements.

Hi Kunjal,

You should be able to see the ellipsis (...) in Backlog or Active Sprints page.

Alternatively, form the url directly like: https://JIRA_SITE_NAME.atlassian.net/secure/RapidBoard.jspa?rapidView=BOARD_ID_HERE&projectKey=PROJECT_KEY_HERE&config=roadmapConfig

Replace
JIRA_SITE_NAME, BOARD_ID_HERE and PROJECT_KEY_HERE with your Jira site-name, board-id and project-id for which you want to enable the roadmap

Please let me know if it works. If required, please raise a support ticket to let us assist you sooner.

Thanks,
Nitin Bhojwani

Hello! I would like to be able to use roadmaps on my classic business project (not nextgen), however I do not see the ellipses to get to board settings (on the board page). Am I missing something? Can someone help me? The instructions on this page (https://support.atlassian.com/jira-software-cloud/docs/enable-and-disable-the-roadmap/) are not helpful since I cannot access the board settings. Thank you!

Hi Team,

I am trying to use Roadmap on classic version but i am getting an error saying "it does not match your board filter". Please support.

I have the same issue with the roadmaps that, it is worth if stories/issues can be included rather than epics. 

This is great news. And i have started to use the feature. Really helps a lot (to start at-least with Beta).

Was so excited to see a beta Roadmap feature available in my Jira board settings, then noticed it only works on Epics, and my board has too many epics to make this work. The fact that this only seems to work for Epics rather than showing Epics, individual Issues and issue Subtasks is a major hindrance. 

@David Hayward - unfortunately you need to pay a whole lot more for Jira Software Premium if you want multiple projects in the roadmap: https://www.atlassian.com/software/jira/features/roadmaps?tab=advanced

Atlassian haven't given an option just to have the Advanced Roadmaps separate from paying for the Premium licence...

Good afternoon. I have been keen to look into using Roadmaps for a while, so a little disappointed that I could not use it in my classic software project because the filter included tickets from projects other than the software project. Is this something you are hoping to address in the near future or should I give up on this?

Thanks

Really liking this new feature, but would be great to see a bit more available on it, such as:

1. Ability to switch a sprint view on and off
2. See releases plotted against the timeline
3. See planned dates / sprint for specific stories within an epic
4. Order stories on the view

Another big thing causing us an issue at the moment is the confluence macro to give a really nice display of the roadmap, only works for roadmaps created in next-gen projects.  Can this macro be updated to allow us to select roadmaps from classic projects and have the interactive view on confluence?

Should the roadmap automatically pull from the board? Mine is currently empty...
Tx!

The Epic and Issue limitation is soon going to create a major problem for us. We are using the Jira add-on Zephyr, which introduces a large number of additional issues and pushes us over in terms of the availability of the Roadmap. This seems to be a decision that provides highly useful functionality only to immediately remove it again. Can this please be reviewed and relaxed?

Hi,

My Feedback -

1. Looks great

2. Can't seem to move created stories up or down on the roadmap, it would be great to enable that flexibility if creating a task later on that should be before another existing one

3. Would be great to use the slider to update start and due date on stories

4. would be great for the stories timings to roll up to affect the start and due date of the epic

5. would be great to show dependancies

I am using only for scrum boards.

Hi, does anyone know whether Roadmaps work for both Kanban & Scrum boards? I did not see the option on either board types so we could activate them. Any idea why? I though it was already available for everybody...

Cool. Thanks for the hint @RyanS. Just aktivated roadmaps... they're looking great.

Malte Hübner - They should be available for you now, they're just not turned on by default. See the instructions above or just click this link: https://confluence.atlassian.com/jirasoftwarecloud/enable-and-disable-the-roadmap-1004952906.html

+1 for adding roadmaps to classic projects. Next gen projects are too simplified

Jonny Wermut: it is Start date and Due date

Which fields does the roadmap use for time?

I think overall there could be value with adding in fix versions to both Roadmaps and other areas of the product such as swimlanes. 

@Nicolas LAINSEY

Yes....Roadmap is based off of "What I THINK I want to RELEASE." Thinking that things are released in "Epics" is not only a very rudimentary way of approaching it, it's also flat out incorrect (especially in today's day and age)

As I might've mentioned elsewhere...has no one at Atlassian read anything by David Patton (User Story Mapping), Roman Pichler (GO Product Roadmap), and any other number of Release Planning templates out there.

Atlassian needs to stop thinking GANTT...pure and simple.

Hi all,

as mentioned above, it would be interesting that the roadmap be based on releases rather than on EPICs (or complimentary to ?).

Glad anyway that this feature is available in classic projects ! Thanks.

Nicolas

f29d818b38fe, you should be able to enable the feature for your board by following the instructions here: https://confluence.atlassian.com/jirasoftwarecloud/enable-and-disable-the-roadmap-1004952906.html - please let me know if the roadmap tab is not visible in your board settings.

731b1805a29f - do you still have issues accessing the roadmap feature?

Thanks,
Albert | Jira Software

Hi - has it been rolled out to all users? I haven't seen any messaging in my Jira and I can't seem to figure out how to configure it if it's available now. Let me know how to get the roadmap in for classic or when I can expect to see it in there.

Thanks,

Kyle

Hello Team, I am not able to see Roadmap option available from today afternoon. Any changes going on?

Thanks to Team Atlassian to add this feature to classic project under standard subscription... Much appreciated.

Product team: Any plans to add into classic roadmaps view by releases? Goal would be to have 3-4 releases or then 14 days (or so) windows would be visible on roadmap. Tickets shown in this in ideal state but that is likely too much etc. I am not talking about advanced reportings and further capabilities coming with advanced roadmaps or Jira Align. This within single project view. It would be quite a bit of help even in classic roadmap.

Wonderful Atlassian Team  

Hi atyutyunnikov - the Confluence macro does not work with roadmaps in Classic projects just yet. We are aiming to roll this out very soon.

i can't add the roadmap from classic project to confluence  (for next get projects works good)

Hi All,

check your board settings in classic projects. You'll see Roadmaps in there to enbable/disable.

Thank you for making this available. it is clear it is the first step. Looking forward to further improvements.

I didn't receive any popup (I'm the admin) how can I be an early adopter? 

I received the pop up but I ignored it.
How do I set up the roadmap for my project? 
Thanks in advance!

@Felipe....If that's working for you, great!

That being said....you know that part in the agile manifesto..the part where it says...

Individuals and Interactions over Processes and....Tools.

There are ways already established (and not by yours truly.....and certainly not recently) that are how a team can be more agile and responsive to delivering what a customer needs. Our tools, may at time promote some change to that, but not in the direction this feature points to.

Speaking as both a CST and AKT, this roadmap promotes a very simplistic proto-kanban approach if you do as you say, but what room does that give your team to more readily inspect/adapt its way towards delivering what's actually going to be needed. The person managing that roadmap will have to do a lot more to keep it up to date, the way you're describing you're using the roadmap feature.

This roadmap feature is no different at present than what was present in the Next-Gen projects almost a year ago. You didn't see people flocking to it then there (probably because there weren't enough brave souls to venture into "Next-Gen" project land). 

The feature as it stands now...has a LONG way to go before it becomes more useful than as a Gantt chart.

 If someone WANTED to work this way...what they'd do is create the roadmap off of VERSIONS, and then drop in the Stories/Tasks INTO those Versions.

After all....we RELEASE different "Versions" of things from a product backlog to the user/customer.....not "Epics".

hi all!

this feature is amazing. we have to modify the way we act with epics a little bit but its amazing! you cannot make everybody happy and expect that it fits everybody. 

I worked with it today and came to this process:

context:

• we work in a kanban approach making versions which are released.
• our kanban board's swimmlanes are grouped by epics

what we did now is to create more epics with the name of the version in there so we have multiple epics for one version. this way we can plan very good and see the process.
it is also very cool that moving the epics in the roadmap changes their priority in the kanban board!

simply amazing
thank you very much

For the ones disappointed: try to adapt your processes to the feature if possible. If not, Atlassian will probably improve this feature in the next months

I can see how this makes PM's excited.

Sadly, this is effectively a Gantt chart for Jira. 

1. I can capture Stories underneath Epics. Fine. yet another way of adding Stories to Epics in a quick and easy way... GOOD.
2. Chaining only Epics to Epics or visualizing chaining epics to epics. Meh. So we can Gantt Epics. IF, in fact, teams were going to build "an EPIC" before moving on to another Epic. Has anyone ever SEEN Story Mapping or User Journeys? Unless you're a "waterflood" or "Epics as phases" approach, an agile team doesn't deliver this way, and a Product Owner wouldn't create a Roadmap this way either.

Hence.....sadly....turning this feature off, lest it create dissonance with our agile teams.

This: https://www.atlassian.com/agile/product-management/product-roadmaps

is not how agile teams create roadmaps.

Someone please read a book by Roman Pichler or Jeff Patton.

We just turned it on for one project, and it seems great so far. I'm very excited, I think this will help our planning and digital project managers a bunch. Thank you!

@Pete Morris. Thanks for releasing this feature.  It really does help with my departments planning and providing visibility to others in the organisation of our programme.  I'm going to stop watching this feature now.  It would be helpful to have more advance filtering features in the future like we have for boards and I would be happy to participate in future roadmap functionality beta testing.