Hi all, trying to figure out the intent of the default fields in Jira Product Discovery, and can't find anything useful in the docs.
How would you describe the use cases for a Goal vs. a Theme vs. a Bucket? How do you use these fields to categorise and prioritise your feature requests?
@Pete Crocker our approach with Jira Product Discovery is we want to give you a toolkit that helps you capture, prioritize and communicate your product ideas, opportunities, decisions, plans, etc. - using a set-up that best suits your particular environment. That's why it's so flexible.
The default project template includes different fields but they are just suggestions to help you understand what the product is for and help you get started.
Feel free to use or change these fields or create your own - that's what the app's here for.
We already had goals that actually aligned pretty well to the default ones Atlassian included. I just added a couple more.
I use the bucket to group together requests mostly base don origin i.e. existing customer, potential customer etc. then factor this into impact weighting.
Not sure about themes? I cant see that field. Unless you mean product area, in which case we use the names for each overarching parent feature in our platform.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events