Bug 173083 - [StatusHandling] Need a way for the user to hold onto errors
Summary: [StatusHandling] Need a way for the user to hold onto errors
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Krzysztof Daniel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 105891 173041 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-02-06 10:21 EST by Tod Creasey CLA
Modified: 2019-09-06 16:15 EDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tod Creasey CLA 2007-02-06 10:21:55 EST
20060206

Currently there is no way for the user to hold onto errors for future reference such as bug reporting.

We should add a button in the error dialog to hold onto the error. There are a couple of suggestions

1) Generate an error in the problems view. The main issue I can see with this is if there is anything (such as launching) that will prompt you all of the time if you have errors. The other issue is how to clear the error. It is possible to do this currently but users are not accustomed to being able to delete errors from the view.

2) Create a "Stored Errors" view where these can be stored.
Comment 1 Szymon Brandys CLA 2007-02-07 09:43:28 EST
"Store error" button
1) can be a part of details part (in the tray) for workbench handler/sdk product handler.
2) can be part of popup menu on the errors list.

"Stored errors" view should be rather a part of a custom product handler.
For instance our SDK can have product handler which allows for storing 
errors in the "Stored errors" view. But for instance Rational in its product handler will show all stored errors in the tray of the dialog.

And if we decide to provide the stored errors view, it should be rather a sample like the bugzilla reporting view.
Comment 2 Tod Creasey CLA 2007-03-19 09:48:57 EDT
This is a priority for M6.
Comment 3 arne anka CLA 2008-02-15 05:31:31 EST
*** Bug 105891 has been marked as a duplicate of this bug. ***
Comment 4 Krzysztof Daniel CLA 2008-04-23 04:00:00 EDT
We are too close to M7 to introduce a new view. However it is possible to do this in custom application by modifying default details or support area.
Comment 5 Szymon Brandys CLA 2008-04-24 07:17:46 EDT
*** Bug 173041 has been marked as a duplicate of this bug. ***
Comment 6 Boris Bokowski CLA 2009-05-06 16:50:23 EDT
Removing 3.5 target milestone. We are in the end-game now. Please have a look and decide if this should be targeted at 3.6.
Comment 7 Eclipse Webmaster CLA 2019-09-06 16:15:42 EDT
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.