I just created a new instance of JIRA to test the roadmap feature into a Scrum project but I can't find Project settings > Features to enable the feature.
Someone can help me with that?
We are running so many classic projects - controlled by 2 admins - we would need all these fancy improvements in the classic projects as well.
What about that?
Is there somewhere a roadmap available for the Jira classic procucts as well - I only can find a atlassians roadmap for next gen projects.
Best regards, Michael.
The Classic / Next Gen choice feels like you need to select the lesser of 2 evils.
In Classic, you don't get a roadmap and in Next Gen you can't change a project lead (https://community.atlassian.com/t5/Jira-Software-questions/How-do-I-change-the-Project-lead-on-a-Next-Gen-Kanban-board/qaq-p/944575)
What would be great is a single product that gives you all this functionality rather than 2 half baked products.
Proceed with Caution! There is a huge difference in classic vs next-gen projects. For me the next-gen showstopper was the fact that once a sprint is completed you are no longer able to access the stories from that sprint. There are many more differences but that is not the purpose of this thread.
I'm really surprised by this limitations. I created my project only a while ago and didn't even know about this limitations. And now I saw the roadmap feature advertised and had so search for long to find this thread telling me that I can't use it. That's a really frustrating and sad experience. I think there needs to be an option to convert/migrate classic to next-gen projects. And besides the roadmap view I really don't see the difference between classic and next-gen.
Currently because of the limitations listed below among other things it is not possible for us to migrate from classic to next-gen. Not the end of the world for now, but I hope to see in the future either improved migration or most of main new features added to both type of projects.
Next-gen projects and classic projects are technically quite different, so a few things can break when you migrate from a classic software project to a next-gen software project. For example:
Epic links and issue links: Any issue links in your classic project will not exist in your next-gen project. The issues themselves will still exist, but the links between them won't.
Subtasks: All subtasks will be lost in this migration process.
Custom fields: These must be recreated in your new next-gen project.
Story points estimation: This data will be lost, however you'll be able to start using story points estimation by enabling the Estimation feature in your next-gen project.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events