-
Sub-task
-
Resolution: Fixed
-
None
-
None
-
None
Hello!
Roadmaps are now out of Beta and will be enabled by default for all new Classic type projects
Once again, thank you for all of your comments and feedback.
In the existing Classic projects you can enable the feature for your board by following the instructions here: https://confluence.atlassian.com/jirasoftwarecloud/enable-and-disable-the-roadmap-1004952906.html
As always, we’re keen to hear your feedback, so please send it in via the "Give Feedback" button in the product.
For those of you who want more from the feature, please stay tuned. Our teams are continuing to investigate and build improvements for both Roadmaps and Advanced Roadmaps based on your feedback.
Cheers,
Deniss Alimovs
Atlassian Product Manager
Original request:
Hi
I would like to use the new feature "Epic Roadmap" in my classic project: https://confluence.atlassian.com/jirasoftwarecloud/roadmap-957979308.html
Do you have some infos on this feature?
Regards,
Timothée
- is duplicated by
-
JSWCLOUD-18097 Roadmap in classic projects
- Closed
- is related to
-
JRACLOUD-91603 Support cross-project usage in Basic Roadmaps for Classic projects
- Closed
-
JRACLOUD-91568 As a project manager, in order to have a big picture of my projects, i need to see epic from different projects in the Roadmap
- Gathering Interest
- relates to
-
JRACLOUD-91434 Date range for child issues on classic roadmap
- Closed
-
JRACLOUD-91435 Ability to view Roadmap (company-managed project) on Mobile app and Jira Cloud for Mac
- Closed
- 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...
-
Page Loading...
[JSWCLOUD-17214] Enable Roadmap for "classic" project
already voted for this feautre but I'm also adding a +1 on comments as well
+1
Exact same issue as all. Currently lack of multiple boards block us from using next-gen projects.
Same problem, next-gen project are too simple to be used for our team : cannot create multiple board on a single project, cannot run our workflow....
Roadmap is a precious tools, and we would be grateful if you add it into classic project!
This feature would truly benefit the classic projects, can you please add? I am not sure, what is the rationale behind not having it for the classic projects, can someone pls elaborate?
Looking forward to using the roadmap feature in my classic projects soon!!
Thanks, this would be extremely useful!!! We tried using next-gen projects but they're just way too limited in functionality, so we're using classic projects. I've been using the Next Gen roadmaps for planning but they don't integrate with the classic projects so it's just not real useful. If this functionality was in classic it would greatly improve our planning process here, couldn't tell you how useful this would be for us!
Agree. Please add this. We are using complex work flows, custom filters that are not yet supported in Next Gen projects. It would be great if we can have this feature in classic.
The frustrating part is - I know ‘just’ is a hated word when specing an enhancement - it should just be a case of adding an epic start and end date to issues in classic projects and let it use the same screens. Next-gen projects just don’t work for ourselves, if they did I probably would save the monthly fee and use Trello with the custom fields power up.
We would really benefit from this. We have looked at Next Gen project, but currently they're some missing features (mostly granular features) that justified that we stay on classic. However, Roadmap is one of the very "strong" value of the next-gen, it would be very useful that this get added to existing "classic projects".
Jira Product Manager - you have received significant feedback about the need for Jira Roadmap for Jira Classic Projects. I think it is time for Atlassian to provide direction and feedback regarding this request, and how Atlassian intents to handle this issue.
Jira next-gen is not an option for us to move to because of the lack of administrative capabilities and ability to interact between next-gen projects. We have over 50 Jira classic projects.
If the idea is to force Jira classic customers to sign-up for Jira Portfolio then this is a bad strategy that is negatively impacting your biggest customers, due the the per-user pricing of Jira Portfolio or its competitor BigPicture.
Please provide us with the courtesy of a response to this ticket.
We would also like this for classic projects. We have only starting using Jira 2 years ago and still are working on "spreading the word" across the enterprise. Also, as others have mentioned, while next-gen is more streamlined, it's not as robust as we need (and I suspect the same is true for many Jira customers).
I do agree with comments above, this needs to be replicated for classic projects, there are lots of functionalities missing in next gen, and it's risky to migrate or use it, so improve the classic one and do not waste time doing a new framework when that roadmap it would be more useful in the classic projects, and try not to ask for money for any simple feature you do.
Don't have information on your business @Atlassian, but I imagine that:
- most of your clients are on Classic Projects
- Jira is used for task management but it's a lot of times used for product management as well
With these 2 assumptions it's unacceptable that the migration to new-gen projects (explained here https://confluence.atlassian.com/jirasoftwarecloud/migrate-between-next-gen-and-classic-projects-957974933.html) is missing so many functionalities. Look, I have thousands of tasks, how exactly do you expect me to match all the relationships again? It's quite un-reasonable and feels again as a half-shipped feature.
In our case BigPicture is just stuffed with a lot of features we don't need. And the costs are a no go.
Also a upvote for the simple roadmap in a classic project.
It's a shame that Atlassian doesn't support Roadmaps for classic projects.
Probably need to shift to some other tool that has builtin support for roadmaps.
is that roadmap the same roadman we are discussing here? And why premium? I am already pasying for Jira Cloud, I have to pay more to use roadmap?? Then I think I would rather pay an addon instead?
@Kenny Dickie @Jeff Fritz - I really hope this isn't the case, that would be terrible news
@Kenny Dickie - it seems a little disingenuous to take a highly upvoted/commented feature and place it into a higher tier premium plan (presumably at a higher cost)
since the next gen projects don't seem to support an enterprise implementation in terms of permissions granularity, I can't use them. Frustrating to see this feature locked off.
[Jira Software Premium|https://www.atlassian.com/software/jira/whats-new/premium]
2020 - Build a roadmap that incorporates work from multiple teams
First, will this new multi-team roadmap be supported in Classic and Next-Gen? Second, will customers be required to purchase Jira Software Premium to get this multi-team roadmap functionality?
Would love to have Roadmap feature in Classic Projects. Classic Projects are still very relevant.
I do think this would be very useful for Classic Projects.
I'll also throw out there it would be excellent if you could also use Releases or Epics as the basis for the roadmap. Releases have start and end dates already, it could be a roadmap view in the Release section.
Agreed, It'll be very useful to have roadmaps for Jira Classic projects.
Would love to have this feature in Classic. Seems like a simple integration considering its already been built for Interactive.
Would like to hear some sort of update on this. This issue should probably be converted to a Story as it's not really a subtask for Next-Gen Projects.
Strategic full stack roadmapping tool https://dragonboat.io/ that I've been using at my company.
Basically it is structured to align strategically, plan/forecast & manage, setting you up to do a cleaner quarterly planning. It lays on top of JIRA. The simple roadmapping tool is fine, but this adds in the layers that are necessary to actually work on the right epics.
Dear Uncle Atlassian, I just want to express that here is another nephew that is super interested in the Product roadmap feature, but due to the nature of the business, we are still using a classic project, and moving towards a next-gen one would cause a lot of friction (customization and all that..and honestly, the fact that we are a small company and no one is really the Jira "admin" ina professional sense of the word). Looking forward to seeing this feature for classic projects
Did Atlassian really just let someone use their comment board for a new feature as a place to pitch and promote his own project? Hats off to you @chuckfoster - you deserve credit for leveraging a captive audience. #noshameinyourgame #getterdone #capitalizeonaneed
Just adding my support here. If we switched to next gen, we would lose a lot of additional configurability that we rely on. If we stay with classic, we can't have a great way of organizing roadmaps. There is already great versioning and epic support; this is the next step for portfolio management in classic projects.
This is key, as Next-Gen Projects will not work for us until well into the year 2020 - https://www.atlassian.com/software/jira/whats-new/next-gen#result-b8046a15
I would like to know what the longer term plan of "Classic" project type is on the Jira roadmap.
This would be amazing... Our team loves the idea of the Roadmap planner, but are worried about the ever changing landscape of the next gen board!
It's could be great if you guys can enable this feature in the classic project, today I'm using Lquidplanner tool and integrate with Jira and it's a mess!! so I'm really exciting to see this functionality into classic project soon!
The idea behind every agile team is to set up their work flow to suit their needs. That usually means a customized workflow. I help teams with Agile transformations. Most teams are transitioning from some sort of waterfall process. So there is usually more granularity with those workflows. I can also see where the next-gen simplified model could be useful. But I don't know of 1 Scrum Master that would approve of "No Product Roadmap" and limited reports - only 2 in the next-gen Model. We need the Product Roadmap Back in the Classic Version! Does someone at Atlassian hate PMs and Scrum Masters? And since the word "Enable" is in the description, it looks like all that has to happen is making visible a few lines of code or a config on/off set to on.
Please "Enable this feature"!
Sorry to bother you but I would like to know the release date as I dont have access to the Calendly app.
Thanks
This is EXCELLENT news Erika. Thanks for providing us with an update on this. It would be a really valuable feature in classic and I look forward to hearing more about your plans for it soon.
Hi everyone,
Thanks for sharing your feedback and communicating just how important it is to connect what you're working on in Jira Software with your roadmap. We're also really happy to hear that the next-gen roadmap has resonated so strongly that people would like to see it in classic projects.
Given your input, we’re currently exploring options for creating a roadmap feature that is compatible with classic projects. We can’t comment on timelines or details of the feature at this stage, but promise to communicate more as soon as we're able.
Your feedback guides everything we do here at Atlassian so we'd love to hear your thoughts about what you'd like to see in the roadmap. If you have time, I'm setting up 1 hour calls [here|https://calendly.com/esa-3/jira-roadmap : to inform our future roadmap.
Thanks again for your passion and engagement and I look forward to connecting with you!
Cheers,
Erika
Atlassian Product manager
Jennifer McVicker, same here. We tried NG specifically for the Roadmap, but in the end had to move back to classic. NG lacks all the other reports that we need.
Its very odd that this feature is released before basic Epic management in NextGen projects!!
Why why why doesn't EpicLink work in NextGen. Its been requested as a basic capability for many months now. And no sign of progress.
Ditto. This would be EXTREMELY useful for Classic projects. I tried to make the NG projects work for my team, but no. They're just awful.
+1 for Classic. This looks great, but NG aren't usable at this time.
Ben Jackson (Atlassian Product Manager) posted a comment on this article yesterday: https://community.atlassian.com/t5/Jira-articles/Introducing-the-Jira-Roadmap-Macro-for-Confluence/ba-p/1123288/page/3?utm_campaign=immediate_general_comment&utm_content=topic&utm_medium=email&utm_source=atlcomm
"For those keen to see roadmapping in Classic I can only say for the moment stay tuned"
So I suppose this means they are considering it.
+1 for Classic. This looks great, but NG aren't usable at this time.
+1 Fully agree this feature is a huge help in keeping an overview.
Perhaps it could be implemented as simply as visualizing the "start date" and "end date" for the (selected) epics in the same timeline?
+1 We also would like this feature. All our projects are in Classic and, as it stands, NG is not an option.
+1 for classic projects. We loved the look of NG projects, but they quickly fell flat because we needed so many features that only exist in the classic projects.
+1 for classic projects. we only use those and would love to be able to use this.
We have encountered blocking issues when classic and next-gen co-exist when we tried creating a next-gen so we will only using classic projects. It's too much effort to migrate everything from classic to next-gen at this time.
We have everything configure in the classic project. Being able to leverage the new features in the classic project is more ideal then creating a brand new project, migrating everything over ans basically starting from scratch
We would like this as well since we do not use next-gen projects (we want to standardise our way of working) - and would like to share these roadmaps with our customers
+1 definitely!
When can we enjoy the Roadmap for the Classic one?!
+1. Solidly behind a roadmap feature based on themes and epics for Jira Cloud users with classic projects (which have significantly more capabilities).
Adding another voice and vote. Please add this for Classic Projects - Next Gen Projects lack the features and customization that the majority of your customer base requires.
Give us the epic roadmap! It is insane that it is not available in the classic version of Jira.
+1 for this.
Why not enable it in Classic Projects?
The next gen project are so limited.
+ 1 ,
It seems like to trying an additional financial burn to the cloud user.
For only to sell more their add-ons.
it's sometimes very disgusting.
Hi @Alvaro Munoz,
Sorry. I haven’t seen your submission. Do you mind submitting again? https://classyroadmap.com/sign-up-for-beta
We’re still deciding the pricing, but it will be very affordable around $5-$10 per user per month.
Hi @Chuck Foster, I signed up for Beta but didn't receive any e-mail or so. How can I start using it ? Also, what will be the price? I cannot find it in the web. Thanks.
Sorry all, I thought I was commenting directly to certain users first. You are all welcome to sign up for the beta of Classy Roadmap at http://classyroadmap.com.
It's very simple to use....
1) Create filters in Jira Cloud for your epics that represent your roadmap projects.
2) Select your Jira "roadmap filter" in Classy Roadmap
3) View, present, share your roadmap in real-time from Classy Roadmap. Updates in Jira can be viewed in Classy Roadmaps in real-time.
Hi Adam,
I noticed you were interested in the request for the Roadmap feature on Jira's Classic Projects. I am tired of waiting on Jira to add the roadmap to classic projects, so I've started working on a small project that works similar to the Roadmap on Next-Gen projects by labeling and filtering epics. As opposed to other similar 3rd party tools, we are planning on pricing our tool by user of our tool, not by active Jira users. If you're interested, you can sign up for the beta at http://classyroadmap.com.
Hi Timothee,
I noticed you started the request for the Roadmap feature on Jira's Classic Projects. I am tired of waiting on Jira to add the roadmap to classic projects, so I've started working on a small project that works similar to the Roadmap on Next-Gen projects by labeling and filtering epics. As opposed to other similar 3rd party tools, we are planning on pricing our tool by user of our tool, not by active Jira users. If you're interested, you can sign up for the beta at http://classyroadmap.com.
+1 don't think I can add anything more than is already said. This is needed.
+1 We are having to have a roadmap that's completely disconnected from our projects. Would be great if we could tie them together.
I'm conscious there have been a lot of comments and votes for this feature. Atlassian responded very early on in the conversation but we've not heard anything else since. It would be good to have further dialogue with Atlassian around this particular suggestion given the interest in it. Are there any moderators keeping an eye on this who can give someone from the company a nudge? Otherwise, this is going to have been open for a year come October with no further direction on whether this can or can't be achieved. In some respects, I'd rather this be closed down rather than spending an eternity receiving emails with +1 in them for no real action or response from Atlassian.
+1 Would be great to have the roadmap on classic projects. There are 3rd party alternatives, but it's so much better to have all the tools in one box! Next-gen is nice and easy, very lightweight and flexible. But some powerful features of classic projects are missing, so it feels quite limiting, especially search & filtering options, reports.
+1
Just started looking into next-gen but seems very limited still
Please add this ASAP! Or at the very least, provide a template on confluence!
Agree with all previous comments, please add Roadmap to classic projects.
Both next gen and the classic fall short in major ways over the simplest features. One won't let you see the roadmap, the other won't let you filter properly. Please consider adding the roadmap feature to classic or open up the filtering capabilities in next-gen.
This feature would be extremely useful to have on existing projects
Christian, I can't speak for everyone but I'm certainly aware of Portfolio. However, for us it's a bit of a sledgehammer of a solution to crack a walnut of a problem that the next-gen roadmap would be perfect for in classic projects.
Just in case nobody mentioned before:
My guess is for the users of classic projects https://www.atlassian.com/software/jira/portfolio is the product that provides roadmap features.
Since Atlassian is selling this for an additional price, I don't think they are creating yet another version of roadmap(s) any time soon.
And please stop putting "+1" as comment(s) every other day: use the "vote for this issue" button instead!
+ 1 from me and our team!)