I would love to get access because I have been searching for a product roadmap tool that has the various integrations to see from ideation all the way to delivery. We used Product Plan previously but hard to manage between various platforms.
This will also provide our stakeholders immediate updates between roadmaps and delivery without having to reach each time they need it.
The goal is efficiency standing and delivering projects rather than wasting time pivoting between different platforms.
I'd love access, as we're currently employing several workarounds and automations to try and accomplish something similar to this, and having it as a built-in feature would hugely simplify our process and improve our alignment between product and engineering.
Hi @Tanguy Crusson I'd love to try this out. In fact, next week I will be doing a demo for the leadership team on how we could implement an OKR system and what that would mean for the technology team. I'm putting together a little demo workspace to illustrate how everything works - together that includes the following Jira products:
Atlas
Jira Product Discovery
Jira
Advanced Roadmaps (Jira Plans)
To be totally honest with you, without the ability to display the Plan/Advanced Roadmap along the same dimensions as in JPD, I'm going to have to do a fair amount of asking my colleagues to use their imagination as I explain how Atlassian can help us set goals, plan initiatives, and deliver results within the goal's timeline...not exactly the "Aha!" moment I was going for.
Granted, its a big help to be able to group by the same Atlas Goals in JPD and on the Advanced Roadmap but often it helps to focus on subsets of projects (ie., initiatives, pain points for a specific type of customer, features to support entering a new market segment, etc) that do not conform neatly to goals, teams, or single initiatives.
Since that sort of thing is actually what JPD is really great at, if I could show everybody how Atlassian would help us all see the whole chessboard, from various angles, with just a few clicks, all the way from the planning phase to release, without having to illustrate my point by asking the CEO to "imagine if this Plan was grouped by customer cohort instead of H2 Objectives...." I believe the value of Atlassian will be much, much more obvious.
We'd like access integration with Jira Plans and Product Discovery roadmap because we use JPD for product backlog and roadmap building and we need integration with Jira Software to set the bridge between Product plans and Delivery process. Also, we need to report on features in roadmap progress to Leadership and customers and this integration will allow to do this without missing data or manual overhead in adding fields.
We'd like access because... we're currently want to be able to understand operational impact of the normal Jira projects within the combination of the roadmap. Currently it is very heavily work to get this insight within all kind of offline files.
Atlassian Team members are employees working across the company in a wide variety of roles.
July 18, 2024 edited
Hi everyone,
We've given early access to about 100 customers who asked on this post up until a few days ago (if we could locate your site based on the URL you provided). If you have access you should see a notification about it in JPD when you open an idea.
To give us feedback about the integration: you can just add a comment to this article.
Limitations:
Ideas are not editable in Plans, only via JPD
Idea preview on hover only show issue key and summary, not other fields yet
Up to 1000 Ideas are supported in a Plan, not a single more
Group by Idea: Idea header might be empty if the data inaccessible
Group by Idea: groups are not alphabetically sorted
@Tanguy Crusson - exciting to see that early access is here! Do have any idea yet when it will be available to more than the first 100? We held off on a temporary workaround, but may need to proceed with it until there is wider access to this capability.
The ability to group by Idea is nice, but for our scenario, we really need it in the Plans hierarchy. In one of our views, we need use a custom field to group the issues, which means that we lose the ability to see the issues for the ideas in that custom field. Ideally, the Idea is at the top of the hierarchy above Initiative.
Is there any chance the link you have to a demo of how the Ideas are reflected in the plans can be made available here directly and/or something other than Google Docs (see below screenshot of the link from above that I'm looking for)? Our company blocks Google Docs access and I'd like to see how this was done (without waiting to get home to dig it up).
One immediate piece of feedback: we're still having the issue where locked date fields (in this case, date fields created for Advanced Roadmaps/Plans) are not available to sync to date fields on Ideas. I opened a tech support ticket several months ago and confirmed this is a gap in the feature. Since that's the primary date field we use for tracking delivery, syncing the dates is problematic.
Hi @Tanguy Crusson an archived idea still shows up in the plan as it had a delivery ticket linked, but of course (by definition of archived) it does not show up in JPD.
What would be the best approach? Just delete the archived idea? Unlink the delivery ticket (as it was linked to another idea)? Apply any kind of filtering in the plan view (which one?)?
We'd like access because... We are in the final stages of our first role out of JPD, which includes the planning of our Big Pieces of work across the business. Moving away from excel and PPT for this purpose. As part of the next phase, I want to use plans to help better map capacity and dependencies and to then connect the work of our teams to deliver the ideas.
Thanks again for giving us access. I wanted to share some feedback I thought might be useful for this particular feature.
Internally, our Jira Hierarchy is setup as: Feature > Epic > Story > etc.
We use Features as a way to link work from across multiple teams, as most releases require heavy collaboration. In our case, we link the Feature issue type to an Idea in JPD.
When grouping a Jira Plan by Idea, it will group the Features correctly under the Idea, however it won't include any children issues underneath it. I'm assuming it's because the children aren't linked directly to the idea.
It would be great to be able to group by Idea, and have all parent > child relationships shows in the grouping.
Current state Jira Plans integration:
Group: Idea 1 - Feature 1 - Feature 2
Group: Idea 2 - Feature 3 - Feature 4
Group: All Other Issues - Feature 1 - - Epic - - - Story
Ideal state Jira Plans integration:
Group: Idea 1 - Feature 1 (linked to idea) - - Epic 1 (not linked to idea) - - - Story 1 (not linked to idea)
We link Epics to our Discovery ideas and then you can see the next level down in JPD based on the Epics being parents of Stories. But this isn't honoured in the plans view if you group by Idea. You only see the Epic and none of the Stories.
Would be good if implemented to honour these parent links as @timothy_lelek describes.
Thanks or the Ideas link, it appears in Advanced Roadmaps as you've outlined and allows Epics/Delivery tickets to be grouped by Idea.
As with some of the other feedback, it would be worth including it in the Parent Child hierarchy which would then show a deeper layer on Advanced Roadmaps
We are getting more and more excitement about leveraging JPD. I would love to offer the teams a way to leverage those within the Jira Plans view for deeper planning once delivery tickets are added to a JPD idea and keep the dots to connected for everyone.
139 comments