3 ms·
Where do you keep those to avoid cluttering the "real" backlog? Separate Jira (if applicable) project?
by halgir 3y ago
Where do you keep those to avoid cluttering the "real" backlog? Separate Jira (if applicable) project?
- stag91 3y agoTossing https://www.getcustomeriq.com/ https://www.getcustomeriq.com/ in the mix - pretty much dedicated to this
- cocoflunchy 3y agoThere are products for those like https://www.productboard.com/ https://www.productboard.com/ or https://harvestr.io/ https://harvestr.io/
- cpeterso 3y agoAnd Atlassian’s own Jira Product Discovery (JPD) backlog management tool that integrates with Jira: https://www.atlassian.com/software/jira/product-discovery https://www.atlassian.com/software/jira/product-discovery
- SigKill9 3y agoProduct management tools typically handle this. Jira Product Discovery and tools like Kitemaker keeps that information close to where the rest of the team works :)
- perlgeek 3y agoEven in jira you can filter your backlog by issue type. (Not saying it's the best approach, separate project and links might work better, because the workflow is different).
- johnobrien1010 3y agoWe have a ticket status in JIRA called "Parked". It allows us to capture the feedback so the stakeholder doesn't feel ignored. And if we get repeated requests, we can find it, bring it out of parked, and it starts to become a real thing. There is the issue of dupes but it avoids the other issue, which is that if you hard decline too many requests from right after they are submitted, stakeholders may stop giving you feedback, which is a bad thing. So it is an unhappy middle ground (which is I feel the normal place which product management occupies. I could setup a small shop in the unhappy middle ground and sell souvenirs.)
- jm547ster 3y agoJira service desk to a separate backlog which is reviewed and filtered.