New "View Issues" Display: Children, SubProjects

ooglek · Post by **ooglek** » 19 Aug 2006, 19:12

Currently, open bugs with children are shown in the "View Issues" as inline, rather than indented in some way to show visually the relationship. Indentation is a great way to logically display relationships.

In addition, Sub-Project bugs are also shown inline with all the other bugs, rather than being separated out.

I'd love to see a redesign of the "View Issues" page go something like this.

Add an additional column before the checkbox column that will identify parent/child relationship. This can go as shallow as one child or as many as are available

When sorted by priority, the bugs that are children of a bug are sorted within that child relationship, but not with all the other bugs. IE a Parent bug of priority HIGH, and a child bug with a priority of urgent, the Parent bug will sort with all top-level parent bugs first, then under that parent bug the child or children will be sorted by priority underneath that parent bug. This way children can have a priority tree within a parent issue, rather than being global.

Any bugs that are in a sub-project go into a separate table, Similar to the Viewing Issues box that currently lives there. A few options here; put each sub-project that is one level below the current project, and show those bugs and sub bugs and priorities in an additional, separate box from bugs in the current project. This keeps it clean, and bugs are listed for sub-projects on that page as well, but separate.

Additional sub-projects below other sub-projects could simply be listed as a small table with Sub-projects with # of bugs, so as not to get lost.

Does this currently exist? It really doesn't change the backend data, just how it is displayed. Is anyone else interested?

This is a rough sketch. I think someone can make it prettier, but you get the idea. SubProjects are not grouped in the parent project, but are still there for you to view, at least 2 levels down: This project, any Sub Projects, and all Sub-Subproject projects and their pseudo status.

Also, any SubProject with all bugs closed wouldn't be displayed; if a SubProject had SubProjects with all bugs closed, they would be hidden as well, unless a config flag said to show them.

Sorts and filters would apply to all bug displays, with the caveat that Parent bugs are sorted with all top-level bugs, then child bugs are sorted separately under the parent.

Consideration should be given to how to sort other relationships, such as "related to", duplicate of or has duplicate. Haven't tested Duplicate yet, so maybe that is handled nicely. Maybe those relationships don't matter in this view.