Tracking bugs and enhancement in Jira Product Discovery

Question

We have just started using Jira Product Discovery to capture, vet and prioritize ideas for the next release / iteration.

If there are bugs or enhancements identified in the current release/iteration, should all work go into product discovery for prioritization or should these small items go directly into the backlog for the next release?

Where I think this could become an issue is in capacity planning. If work is in multiple places, don't want teams to be over-capacity.

How have others handled this?

Hannes Obweger - JXL for Jira · Answer

Hi @Terry Goertz

just adding to @Kit Friend's answer: Issue linking is indeed a great way to keep issues from JPD and JSW projects connected to each other - however you are correct that it can be challenging to keep an overview across all your relevant tickets. Jira doesn't have a great view for this IMHO, but if you're open to solutions from the Atlassian Marketplace, you'll find options there.

E.g., this is how a cross-JPD-JSW overview could look in the app that my team and I are working on, JXL for Jira:

For context, JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a number of advanced features, including support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting.

Since issue hierarchies can be based on issue links and/or Jira's built-in parent/child relationships (like epic/story, or story/sub-task), you can easily model a system where ideas sit at the top, and implementation work for these ideas is nested below.

Any questions just let me know,

Best,

Hannes

Kit Friend · Answer

Hey Terry,

JPD is really designed for the initial funnel and high level roadmap view - for linked work and bugs etc you're better off planning them in Jira Software using the linked Delivery ticket functionality - the source of truth for capacity planning etc should be there.

On some clients we've triggered the automated creation of linked delivery tickets once JPD items reach a certain stage which reflects them being ready for capacity to be allocated etc.