Hi everyone ◡̈
I recently introduced JPD to the rest of my team, and they really are a fan like me. Of course, there's a few hiccups and things that "other tools do more/better than JPD", in their resp. opinions ;-)
One of those was, however, a valid point that I'd like to ask your take on: Hierarchy field.
What i mean by this, is 1 field where there's a bunch of (expandable) options to select from. F.e. with clothing, you have 3 main categories (male, female, kids) that would drop-down further into (underwear, pants, shirts, accessories), and where shirts would drill deeper into (t-shirts, tanktops, button-down shirts, etc.)
I'm not saying i need the list to be that extensive, but you get the gist. The more we work with complex topics and products, the better it can be to be more specific.
In this example, if our customer support reports many "men" related ideas into JPD, as a PM i would want to quickly and easily group them further to better understand the exact needs of our customers.
Is there, therefore, a way to get to this list? one way i could think of, but did not manage to successfully set up, is to link multiple 'select' fields to one another with IF conditioning.
More (early) info / answer to this topic from Tanguy (loving your loom videos btw!!): https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Roadmap-view-and-nesting-features/qaq-p/1926194
Hi @mike_staal , I believe that's what Jira calls "cascading field values" and you're right : we don't support it yet. But thanks for the feedback - I can totally see how that could be super useful
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.