We'd like access please. We heavily use Product Discovery and Jira Plans across our business. This integration closes the loop between Product Management and Delivery for us. This was be a great feature and integration for us and will help our business teams to track our ideas and long term plans.
We'd like access because we actively use JIRA discovery to lead all product initiatives, present to business leaders and more. We are now starting to try and use plan to drive our planning exercises, so this is perfect timing. We would be learning JIRA Plan as we do this.
We'd love to try this. Currently we are starting to plan and track delivery of JPD ideas in Plans and without JPD groupings on at least the epic level I'm finding the need to switch between two screens to track this. It would be awesome to have access to see if this can be more efficient.
Hi - would absolutely love to be part of the EAP. This could solve a bunch of our problems when it comes to sharing info with stakeholders in a consistent way.
Hi, we would love to get early access to this, as we make heavy use of both JPD and Advanced Roadmap currently and with automation rules to try to get tickets in both places synced.
however often the views we use on advanced roadmap can't represent what the business teams see on JPD so it become rather disjointed and unfriendly to use. Having a well-integrated toolset between JPD and Advanced Roadmap would make it easy for all users from both sides of the camp. looking forward to it.
Hello, We currently have 30 Engineering team with plans in AR, and 5 JPD projects trying to link work to the delivery side. Auspost would love to work with you to test out this new capability at scale. Our URL is: https://australiapost-productengineering.atlassian.net/
We'd like access because it will help us better align ideas/opportunities to product backlog in one view and help better connect both worlds. This is important in two contexts: 1- Management or Leadership Planning 2- Teams better connecting the dots and understanding the why relatively quickly.
We'd like access because there is a never ending argument on why JIRA plans and JPD. we are planning to move away from Aha! which is our current roadmapping tool to JPD. If we can get hands to try this holistic view of Product Strategy goals to delivery status it is going to be a Great Potential to sell as a bundle :)
We'd like access please as we've been using Plans for a while to track roadmap delivery and are now starting to use Product Discovery so would like to see how we can track from ideation to delivery in one timeline.
We'd like access because we need to be able to match the many ideas and delivery tickets for planning and to bring in any software tickets that aren't listed in ideas but should be.
We're in the middle of considering JPD for broader adoption within our product organization
The link between Plans and JPD will help us bring some structure to some of our more junior product managers, while also enabling our director to scale up to manage a larger team
Help support a bit of momentum where we are trying to differentiate Product effort (proposed to be done in Jira) vs. Development effort (currently locked by org policy to Azure DevOps). This should help a few more of us stay sane and embed some better working practices.
I'd like to continue the journey for my overall team and peers of pointing out how the right tools can help generate order from chaos (over time) and are worth investing in. It feels like Plans/JPD will give us some good stable ground to build from.
For us, Plans are one of the essential features of our planning process. It will also be much easier to connect with ideas, as we also use it a lot for idea scoring and tracking.
Our COO mandates that we present 18 months roadmap ahead as a Gantt chart, so that the near term deliverables and the long-term strategic initiatives can be seen in one flat timeline. So, in effect, our strategic Now-Next-Later view has to be translated into a quarterly view regularly. I don't love it, but it's the reality.
More ideally this would dovetail with Atlassian Home (née Atlas) and we could specify future goals there, but I find that planning themes/objectives to pursue in the future is poorly implemented. So instead I use JPD to capture themes/objectives that we're considering taking on in the future.
I'd like access JPD integration with Jira plans because:
I lead trainings about Atlassian products (including JPD) to various Atlassian customers and need this feature to show consistency between Atlassian products and features
We are Atlassian partners and need to be ahead of things
We'd like access because we utilize the Plans view frequently and want to ensure our upcoming work is tied to an Idea, and vice versa, in a single view.
We'd love to test this capability as we continue to implement JPD throughout the organization. We're looking to use Plans to enhance our roadmapping and timeline management, and this integration sounds like it can bring a ton of value.
We currently have a 2-event quarterly planning process.
We use JPD for a Portfolio Review which is where we get alignment with commercial teams on priorities for the next quarter. Teams then break down the prioritized ideas into epics (linked on the delivery tab).
We use Plans to facilitate the logistics of aligning the epics to teams, sequencing, capacity management, etc. Right now there is nothing to visually link the ideas and epics, so it makes it difficult to ensure the epic prioritization aligns with idea prioritization (especially when an idea has multiple epics). We were about to try to improve this through using Initiatives as a parent issue that would be 1:1 with ideas, but would prefer to not have to add in another thing to keep in sync.
We use JPD for communication of the product roadmap (Now, Next, Later) and this is working well for most stakeholder management. Our visibility limitation is to tech and product leaders as well as program managers that need more detailed views into the actual delivery so they know if planned and actual team allocation aligns with business priorities, cross-team and cross-idea dependency management, risk areas, etc. Right now this is a flat list of epics and hard to understand which work connects to which roadmap items in JPD.
We'd like access because we need the connection to be greater and more integrated from JPD to Jira. We are loving JPD but this is a missing piece at connecting the 2 to make the roadmapping really useful.
We'd love access as we actively use JPD across the product team, and we're looking for a way to use it for better planning and communication! We can see this integration can bring so much value :)
JPD has become an integral part of our quarterly planning process. We track 130+ ideas across 15+ teams with linked delivery tickets per quarter.
In the past I have discussed with Rohan and Chris about how ideas on advanced roadmaps would fill a gap for us. We currently use initiative tickets which map 1 to 1 with our idea tickets solely to allow us to track ideas via advanced roadmaps. This has been very clumsy.
Would definitely love to beta testing and share our findings if interested!
We'd like access because we are extensive users of JPD and AR and we are in the process of revising our product portfolio process, so it will be useful to test it
123 comments