Ideas should be grouped in multi-level "Core User Needs"

[Alexandre Krammel]

Hi,

A good practice when collecting and organizing Ideas (Features) is to have them grouped in multi-level folders that represent core user needs the underlying feature ideas address.

JPD should have a "multi-level" issue type for core user needs.

Notice in the below example that core user needs may be decomposed in many levels until the idea level, so ideas (leaf level) can bem from level 1 to level "n"

Example of Core User Needs and Feature Ideas:

• Arrange a Vacation Travel
  • Have an Hotel for the Travel
    • Hotel Search
    • Hotel Booking
    • Hotel Payment
  • Have a Flight for the Travel
    • Flight Search
    • Flight Booking
    • Flight Payment
  • Pay for the Travel
    • Financing
      • Search for Financing Proposals
      • Sign Financing Proposal
    • Payment Checkout
      • Credit Card
      • Cash
      • Account-to-Account

[Abby Kiesling]

+1. 

This is holding me back so much from building out JPD the way that will integrate with our other projects while showing the accurate roadmap. 

[Krishna Vempati]

100% - waiting for the day hierarchies are supported on JPD.

[Rohan Swami]

Hi @Alexandre Krammel in case you haven't seen it, we have a post on how best to do this with the current capabilities of the product. See the section titled "Can we create different issue types and their relationships? (e.g. parent/child or opportunity/solution)" on this page.

Rest assured this is in our plans for the future.

[Abby Kiesling]

Unfortunately, that's not functional for large teams that need to build hierarchies based on Epic v Story tickets.  Ideas are stories, and we can't very well have HUNDREDS of options in a field for each epic we create.  That's just not feasible.  And furthermore, we can't tie an individual field option to an epic on another project.  

Can you please let us know when a true hierarchy will be supported in JPD?  

[Rohan Swami]

Hi Abby, we announce all new features here in the Community, keep an eye on these pages.

[Karen Aiken]

The current solution doesn't work well for our team either - 

• it mixes metaphors in a single list - can't configure fields separately for "opportunities" and "solutions"
• requires manual synchronization to keep the opportunities' names in line with the picklist
• doesn't enable nested opportunities, to refine the overall opportunity into needed specifics (eg, Line of Business, Region, Customer Segment)

Hoping for true hierarchy one way or another - for now - our team could get by with a single level of refinement via subitems on ideas. That wouldn't cover all use cases but it would be a start.

[David Nadri]

+1

Agree that some form of multi-level hierarchy within JPD is needed in place of using the current flexible fields/views approach. Glad to see JPD team considering it on their roadmap.