Bug 368362 - Problems view allows optional further grouping based on some patterns in description
Summary: Problems view allows optional further grouping based on some patterns in desc...
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.2   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2012-01-11 10:33 EST by Winnie Lai CLA
Modified: 2019-11-14 03:31 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Winnie Lai CLA 2012-01-11 10:33:00 EST
Build Identifier: Version: 4.2 Buid id: I20111209-2100

In problem view, the grouping currently is based on severity, that group items into errors group, warnings group and information group.

We want an extensible API way that allows plugins to group items by other characteristic and let users to decide which grouping options to be used.

One particular use case is that we can group by severity, and we further group items with a group (e.g. errors group, warning group, etc.) by some patterns in the descriptions of those items.


Reproducible: Always
Comment 1 Winnie Lai CLA 2012-01-11 12:47:55 EST
I would like to implement this enhancement. Could you point me to the repo that I should start with? Is it on egit or the cvs repo?

Thanks.
Comment 2 Paul Webster CLA 2012-01-11 12:55:31 EST
See http://wiki.eclipse.org/Platform_UI/How_to_Contribute

The repo you want is git://git.eclipse.org/gitroot/platform/eclipse.platform.ui.git

This repo is also available on github at http://github.com/eclipse

You can work in the master branch.  The starting place is the org.eclipse.ui.ide plugin and the ExtendedMarkersView.

PW
Comment 3 Lars Vogel CLA 2019-11-14 03:31:20 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.