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
Is your feature request related to a problem? Please describe.
I am using CodeChecker to categorise a considerable (upper hundreds) amount of bug reports. Normally, I filter for the bugs that are not yet overviewed, and then I open the first one. Then, I like to go over all the bugs in the current file shown in the left-hand view. Some of these bugs, however, are already reviewed, so opening them is a useless act (and also the fact of having been already reviewed is not immediately apparent, see #3026). Some or all of the reports in a file could be reviewed already due to having been reviewed in another run earlier.
It is worth noting that the "reports in the current file" view does not respect some of the filters set when opening the report view (e.g. if I'm listing only Unreviewed reports and click on a file, I get to see Confirmed reports too), but also seems to at least respect the run filter (i.e. even though there are "more" reports to the file in another run, I'm not seeing those).
Describe the solution you would like
Next to the "detection status" icon, the "review status" for the report should also be shown. (In my current work, the detection status feature does not make sense, as the bugs being categorised will never really be fixed and the project will never be reanalysed, so everything is New in terms of detection status).
There's plenty of space to show the icon, because right now this list shows no indication to me which is the "next" unreviewed bug in the file, as this is just a list sorted by line number.
Please excuse my horrible paint job:
Describe alternatives you have considered
Grouping the bugs in the tree first by review status, and then by severity. This could be even better, coupled with a logic that opens the trees for the "outstanding" stati automatically when a file is opened, while "hiding" all the review-handled reports in closed subtrees. In case I wanted to go back to previously reviewed bugs, I could just open those subtrees.
Is your feature request related to a problem? Please describe.
I am using CodeChecker to categorise a considerable (upper hundreds) amount of bug reports. Normally, I filter for the bugs that are not yet overviewed, and then I open the first one. Then, I like to go over all the bugs in the current file shown in the left-hand view. Some of these bugs, however, are already reviewed, so opening them is a useless act (and also the fact of having been already reviewed is not immediately apparent, see #3026). Some or all of the reports in a file could be reviewed already due to having been reviewed in another run earlier.
It is worth noting that the "reports in the current file" view does not respect some of the filters set when opening the report view (e.g. if I'm listing only Unreviewed reports and click on a file, I get to see Confirmed reports too), but also seems to at least respect the run filter (i.e. even though there are "more" reports to the file in another run, I'm not seeing those).
Describe the solution you would like
Next to the "detection status" icon, the "review status" for the report should also be shown. (In my current work, the detection status feature does not make sense, as the bugs being categorised will never really be fixed and the project will never be reanalysed, so everything is New in terms of detection status).
There's plenty of space to show the icon, because right now this list shows no indication to me which is the "next" unreviewed bug in the file, as this is just a list sorted by line number.
Please excuse my horrible paint job:
Describe alternatives you have considered
Grouping the bugs in the tree first by review status, and then by severity. This could be even better, coupled with a logic that opens the trees for the "outstanding" stati automatically when a file is opened, while "hiding" all the review-handled reports in closed subtrees. In case I wanted to go back to previously reviewed bugs, I could just open those subtrees.
The first option (just showing two icons instead of one) seems easier to implement, as all the data needed should be available already.
The text was updated successfully, but these errors were encountered: