What's the best way to handle Test Sets in Jira's Backlog?

Other Questions Jira
1

I’m having trouble managing my Jira backlog. My QA team added a ton of Test Sets to it. Now I’ve got way more items than I can handle.

I usually keep my backlog neat with about 80 items. But now there are over 600 Test Sets mixed in. It’s making things really messy.

I’m not sure what to do. Should I just ignore them? Or is there a better way to deal with all these Test Sets?

I want to keep my backlog clean and easy to work with. Any ideas on how to manage this situation? What’s the right way to handle Test Sets in Jira?

Thanks for any help you can give!

2

I’ve faced a similar challenge with Test Sets cluttering up our Jira backlog. What worked for us was creating a separate project just for Test Sets. This way, they’re still in Jira but don’t overwhelm the main backlog.

We linked the Test Sets to their corresponding user stories or epics in the main project. This maintained traceability without the clutter. Our QA team could easily access and manage their Test Sets, while the development backlog stayed clean and focused.

Additionally, we used JQL filters to create custom views. This allowed team members to see Test Sets when needed, but keep them hidden during sprint planning and daily work.

It took some initial setup, but it’s been a game-changer for our workflow. The backlog is manageable again, and everyone can find what they need efficiently.

3

In my experience, the key to managing Test Sets in Jira is separation. We implemented a two-fold approach that’s been quite effective.

First, we created a separate Jira project specifically for Test Sets. This keeps them organized but out of the main backlog. We then use issue linking to connect Test Sets to their relevant stories or epics in the primary project.

Second, we leverage Jira’s powerful JQL functionality to create custom filters and dashboards. This allows our QA team to easily access and manage Test Sets when needed, while keeping them hidden from the main backlog view.

This setup maintains traceability and accessibility without cluttering the backlog. It required some initial configuration, but it’s significantly improved our workflow efficiency and backlog manageability.