You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The product and organization pages show the total counts of issues, vulnerabilities, and so on:
To quickly recognize which items (repos or products) need attention, it would be nice to also show the stats for each item in the list, for example, by showing the icons with colored numbers next to them. Mabye on the right side next to the last status, or on the left in the free space next to the repository type.
The text was updated successfully, but these errors were encountered:
by showing the icons with colored numbers next to them.
Could you create a mock-up for this? I'm not sure I understand what you mean.
mnonnenmacher
changed the title
Show stats for each icon in product and organization lists
Show stats for each item in product and organization lists
Jan 3, 2025
The basic idea is like this, but in beautiful:
The details need to be figured out, like if the icons should be colored or the numbers only be shown on hover, and of course where exactly that should be shown.
The background is that I tested these views today and really liked the summaries, but my test product has a dozen repositories and I was wondering how to quickly figure out which of them have all of those issues or vulnerabilities.
I like the idea, and I think that's doable. To not clutter the ui too much and get a rough overview in one glance, I'd just use the icons and total number of corr. items, without coloring. Then maybe show the item distribution (by severity, for example) on hover.
The product and organization pages show the total counts of issues, vulnerabilities, and so on:
To quickly recognize which items (repos or products) need attention, it would be nice to also show the stats for each item in the list, for example, by showing the icons with colored numbers next to them. Mabye on the right side next to the last status, or on the left in the free space next to the repository type.
The text was updated successfully, but these errors were encountered: