Biggest Limitation with Jira Product Discovery

[@ApetechTechTutorials]

To get more resources and get in contact with me check out this link linktr.ee/apetech

[@AlexanderBechte]

100% this is something I also faced recently when using Advanced plan and I was expecting Ideas are above Epics.

[@ApetechTechTutorials]

Would be so cool if it worked that way!

[@Marc-Brickley]

I agree Alex. The point of JPD was to provide the concept of an opportunity backlog (something that was lacking in Jira) in the traditional manner us product people manage it. The opportunity backlog gets decomposed into smaller pieces (Product Increments, Epics, Stories, etc), and being able to view the traceability through the entire hierarchy of the decomposition is an important. I will admit, this may not have been a miss on Atlassian's part though. In Agile development you ship incomplete products if they solve problems and provide value to the users. I have gotten immense value from JPD without having the full hierarchy (but I don't use timelines, as it is more of a Project Management tool than an Agile tool). It is possible that the full traceability is on Atlassian's roadmap but it is just part of Product Increment 2 🤷‍♂

[@CarlosTejadaWork]

Alex, thank you for this!

[@ApetechTechTutorials]

Thank you very much for watching! I hope you enjoyed

[@DuncanCrowell]

On another note I would be really keen to see a video around your views of how Jira Product Discovery and Jira Align should (if at all) work together. There is certainly overlap in these offerings (albeit Align being far more comprehensive in the Enterprise delivery space and enables insights into delivery - but you also pay through the nose for it) and not seeing anything from Atlassian around the target market for these tools.

[@robertwen-releaseteam6820]

Good catch! JPD Ideas have direct mappings to JSW Epics as peers or parents. This smells like a hole in requirements during development.

[@north-mexican]

Hey Alex, I agree with you: However, I am questioning your why it is that way. Yes it is a Team managed project but moreover, they have added a new link relation: Implements in the front-end or "polaris" in the back-end. This is the link when you are adding or creating a Delivery Ticket. My guess is that this relationship was not rolled out into all hierarchies in the tenants.

[@thorque73]

The decision to implement JPD as team-managed project is really a bad one. Since this so much things doesn't work: no access to custom fields, missing access via REST, no create a JPD-Project on base of another one.

[@Thorin632]

Please make video about Jira and PowerBI integration. Without using third party apps. A complete tutorial to show step by step how to connect them

[@ApetechTechTutorials]

That's not possible as PowerBI is a Microsoft thing and Jira is an Atlassian thing. Naturally, you'll need a 3rd party app since PowerBI is a 3rd party to Atlassian.

[@DuncanCrowell]

This is interesting - working through how my organisation expects to use JPD its becoming more like an Idea can become anything depending on where its born from and how big it is. For example, There may have been some direct feedback of set of feedback that turns out to be a simple CI fix, in which case we may just link it to a single story associated with a live initaitive in Scaling phase. There may be another bit of elaboration that ends up just being a new feature, or it could just be a bug thats landed in JPD via feedback. JPD has become more of a pre-delivery playground that keeps Jira Software clean and just populated with validated items we are actually delivering, JPD then becomes the place we can visualise all that into Roadmaps and lists for stakeholder consumption. So in our case the hierarchy you mention does not matter and an Idea is an Entry point to a complementary and linked Epic, Feature, Story or Bug. We also don't utilise Advanced Roadmaps rather opting for the JPD Roadmap offering.

[@marqwilkinson]

This. One of the nice things is showing and discussing the sum of feature work independent of hierarchies that are specific to software teams.

[@mycomputerlady]

Do you have a JIRA ticket open that we could upvote? If so, can you link it?

[@LesliePrice-u6b]

Stories and other types can also be linked to Ideas..... hmmmm I'd prefer that hierarchies are kept and agree that Idea -> Epics -> Story -> Task..... and not like in JPD directly from Idea link to i.e. Task.

[@AnjaliKundra]

Does it make sense to go from Jira Product Discovery right to creating Epics, Issues, Tasks? Wouldn’t there be a planning stage where the PRD is written, maybe in Confluence?

[@MauricioHeberle-l6n]

Jira needs to allow custom hierarchies.

[@RudyHoltkamp]

I agree with you, Alex! This should definitely be possible. An idea is just another issuetype, which you should be able to place somewhere in the hierarchy. Now the idea and the epic are linked, as 'implements' as you can see kzbin.info/www/bejne/eIXHdItuacmGis0 in your video.