Do all changes need to be added to Jira product discovery?

[Kara Nadarajah]

I'm looking at using JPD. We have some changes which we just need to get on and do as soon as they are raised, there's no need to e.g. rank them against other changes. Is it recommended to add these changes to JPD as well as Jira Software even though there's no research etc. required?

I'm trying to figure out if we need to add absolutely everything to JPD and stop users raising tickets directly in Jira Software or whether some changes can still be raised directly in Jira Software.

If we allowed users to continue to raise changes directly in Jira software, I assume that the JPD roadmap wouldn't display these?

[Hermance NDounga · Accepted solution]

Hi Kara, 

Jira Product Discovery has been designed to handle "large initiatives", or ideas that needs ... discovery 😅 . So we haven't designed it as a "bug tracker" in the sense that small stuff that don't need to prioritized, where you don't really need to have various user imputs to make your mind on what's the best solution etc... can skip Jira Product Discovery and directly go into you enginers backlog. 

To give you a real exemple on how we do it in Jira Product Discovery: I'm in charge of a feature called "global fields". This is an idea in our Jira Product Discovery project. After we released this feature we got feedback but I will select just 3 of them for the exemple: 

• Feedback 1: I would like to make it easier to migrate my values from project-scope fields to global fields -> I created a new idea in my Jira Product Discovery project because this doesn't exist at all, we need designs, and I wanted to check if we have a "lot of demand" for this before investing in this utility
• Feedback 2: When I delete a global field, it still appear in my list of fields -> That's clearly to fix, no question -> I send it directly in the Jira backlog
• Feedback 3 coming from our design teams: We need to change the 🏢 icon to a tag saying "Global" -> That's not a bug, but it's to harmonize with the rest of Jira so it needs to be shipped so it goes also directly in the backlog. 

Worst case, if someone raise a Jira ticket, skipping JPD because they think it will be a small stuff and after engineers reviewed, it's actually not the case, nothing prevent to just move that ticket into Jira Product Discovery. 

I hope it helps, 

Cheers, 
Hermance
Sr. Product Manager @ Jira Product Discovery