nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How do YOU display your active issues?

Esther Strom

This isn't a technical question so much as a request for info sharing. What's the best way you've found to keep track of multiple projects? I'm our Jira admin, but I'm also a web developer. I hate having to switch between dashboards, so I currently have a single dashboard, single column width, and a Filter Results gadget for each separate project I work on (because I need different columns to be visible for each.)

This has worked well, but as I'm added to more projects, it means a ton of scrolling.

Share with the class your favorite way of displaying a ton of information.

Comments

Peter DeWitt

@Esther Strom, I use a board (Kanban or Scrum) and setup swimlanes to represent each project. The list can be long but the swimlanes are collapsible. I also use a swimlane at the top for flagged issues so that ones I need to keep a better eye on are at the top.

Mizan

We work on a Kanban board and have a quick filter "Assigne to me" . The query for this quick filter is Assignee =currentUser() .

Scrumbler

I'll +1 @Peter DeWitt for sure, a Board of any type will serve you well. It compresses a ton of information in a nested style that will allow you to see everything from whichever angle you could imagine. I have a "Sprint" Board designed for everyone in my development pods to use, and then I have a super-powered admin focused one that I hide from them for my own use. Here are some screenshots of each:

Sprint

sprint board example.PNG

Admin

super sprint board example.PNG

I am heavy in on the use of Quick Filters, but at the same time make sure to use your Versions and Epics tabs on the left hand side as well, which are built in. It's worth noting that I get the greatest use out of these because I use a base filter for the Board that is as open as possible and because I ask myself ahead of time what PRECISELY I will want to see. Dashboards, with particular use of Filter Results gadgets, can turn into a grocery store of data that you sift through once you're there and hope you find something useful.

Search for data in the same way you would write a User Story and you'll hardly go wrong.

Patricio Rivera

As many of you I think a custom board can resolve the problem.

I created a new board for all developers with all the active scrum projects on the board filter with stories as swimlanes (You can use projects instead as Peter does too). You can use colors and filter to make it even better.