Bugzilla – Full Text Bug Listing
| Summary: | Triage ergonomics | ||
|---|---|---|---|
| Product: | [Technology] EPP | Reporter: | Ed Willink <ed> |
| Component: | Automated Error Reporting Client (AERI) | Assignee: | Project inbox <recommenders-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | marcel.bruch |
| Version: | unspecified | Keywords: | triaged |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows NT | ||
| Whiteboard: | |||
|
Description
Ed Willink
Can you please provide the bug ids (if available) and the problem ids for triaging? I tried twice unsuccessfully to create a Bugzilla from: https://dev.eclipse.org/recommenders/committers/confess/#/problems/54f2f9b1e4b0eb19d1a16fca/details I followed the 'normal' steps and created bug 461189 from the web ui. My steps: * Go to triage page * click on 'Report to Bugzilla' * In the modal dialog select the product (MMT.QVTd), component (Engine) and version (unspecified) * Clicked ok and got a new browser tab pointing on newly create bug in Bugzilla. I did not receive an error email and thus unfortunately can't tell what went wrong (everything that fails with an exception get's logged and send to me by email). So I've to guess: Did you select a <product, component, version>? Maybe there was an inconsistency which caused the "Create Bug" action to fail silently. If you could try to reproduce with a different bug, I'd be thankful to get more insights. At the moment I don't know where to start looking at. Found a potential cause. Whenever you select a product the component value was became invalid although it displayed the right labels. Thus, if your problem occurred whenever you selected a product but used the default component automatically selected by the web ui, then this should be fixed now. The change is rolled out. Closing this issue. Please reopen if the problem persists. (In reply to Ed Willink from comment #0) > Does the different red/blue background of the "Save"/"Report to Bugzilla" > buttons signify something interesting in this/any respect? You can either associate an existing bug with a problem (by entering a bug id and pressing save) OR create a new bug report from the data available in the report (report to Bugzilla). I changed the placeholder for the empty bug id field and made the bug fields plain text fields instead of form elements to make more clear that there are yet not many editing options. Hope that helps. If not, I'm happy to hear your recommendation how these UI elements would have been more self-explanatory. > What does talkback really do? I can see my comment but is there more? I > would like to see something more like an IMS log so that I clearly see my > message labelled by me and in due course response messages. I'm not familiar with the term 'IMS'. Are you requesting a forum integration as [1]? Sorry if I miss the point. [1] http://try.discourse.org/t/how-do-i-reply-to-folks-here/51 > How do I triage duplicates? See bug 460193 on how to mark a problem as duplicate of another problem (short: you can't but you can link it to the same bug ids and mute it). > I can see a list of similar incidents, but I > cannot influence it. Maybe there is a misunderstanding in the terms problem and incident. Did "The Reviewers' Guide" at [2] help clarifying terms? [2] https://dev.eclipse.org/recommenders/community/confess/#/guide (In reply to Marcel Bruch from comment #4) > > Does the different red/blue background of the "Save"/"Report to Bugzilla" > > buttons signify something interesting in this/any respect? I understand the words. It is the colors I do not understand. If they are meaningless, be consistent. If they are meaningful provide hovertext or equivalent to discover the meaning. > > > What does talkback really do? I can see my comment but is there more? I > > would like to see something more like an IMS log so that I clearly see my > > message labelled by me and in due course response messages. > > I'm not familiar with the term 'IMS'. Are you requesting a forum integration > as [1]? Sorry if I miss the point. > > [1] http://try.discourse.org/t/how-do-i-reply-to-folks-here/51 Instant Messaging System: e.g. The kind of name:text sequence you see in Skype. (If you want to provide SmartPhone-style message bubbles great, But I do not require that. Just a visual feel that a 'chat' is in progress. > > > How do I triage duplicates? > See bug 460193 on how to mark a problem as duplicate of another problem > (short: you can't but you can link it to the same bug ids and mute it). > > > I can see a list of similar incidents, but I > > cannot influence it. > > > Maybe there is a misunderstanding in the terms problem and incident. > Did "The Reviewers' Guide" at [2] help clarifying terms? > > [2] https://dev.eclipse.org/recommenders/community/confess/#/guide Not really. The precise parent/child relationship between incident and problem is vague. Presumably an AERI contains many problems. A problem contains many incidents and may have an associated Bugzilla. Please show us the model. It is much easier if you show it than for use to deduce it. But the link from my email is to an incident titled "Problem Details". Confusing. Provide web pages that are clearly Problem or Incident, with up/down/sibling navigation between them. Suggest that the email link to the "All Incidents" page showing the number and chronological list of all child incidents immediately, perhaps with 'hide-me' checkboxes, but none of the irrelevant watchers.... Then the "Triage" page deals with progress. "Details" if someone really cares. (The stack trace is generally too big for one screen so putting it on the landing screen is counter-productive.) (To allow more control you might permit a ProblemGroup to reference many Problems and so hide the duplicates.) The "All incidents" page could usefully have per-incident icons for "identified user" blue/grey head, "has-user-comment" comment bubble. (In reply to Ed Willink from comment #5) > (In reply to Marcel Bruch from comment #4) > > > Does the different red/blue background of the "Save"/"Report to Bugzilla" > > > buttons signify something interesting in this/any respect? > > I understand the words. It is the colors I do not understand. If they are > meaningless, be consistent. If they are meaningful provide hovertext or > equivalent to discover the meaning. Created bug 461220. > > > > > What does talkback really do? I can see my comment but is there more? I > > > would like to see something more like an IMS log so that I clearly see my > > > message labelled by me and in due course response messages. > > > > I'm not familiar with the term 'IMS'. Are you requesting a forum integration > > as [1]? Sorry if I miss the point. > > > > [1] http://try.discourse.org/t/how-do-i-reply-to-folks-here/51 > > > Instant Messaging System: e.g. The kind of name:text sequence you see in > Skype. (If you want to provide SmartPhone-style message bubbles great, But I > do not require that. Just a visual feel that a 'chat' is in progress. There is yet no feature planed that supports such a behavior. The details page, however, allows committers to contact all reporters by email (single click) for follow up questions. The talking back options yet only affect the UI notifications inside the Eclipse IDE (popups requesting more details etc.) > > > > Maybe there is a misunderstanding in the terms problem and incident. > > Did "The Reviewers' Guide" at [2] help clarifying terms? > > Please show us the model. Created bug 461221 > But the link from my email is to an incident titled "Problem Details". FWIW, it's actually a problem (which has an initial or opening incident). But it boils down to better documentation of the domain concepts. > Confusing. Provide web pages that are clearly Problem or Incident, with > up/down/sibling navigation between them. Suggest that the email link to the > "All Incidents" page showing the number and chronological list of all child > incidents immediately, perhaps with 'hide-me' checkboxes, but none of the > irrelevant watchers.... Then the "Triage" page deals with progress. > "Details" if someone really cares. (The stack trace is generally too big for > one screen so putting it on the landing screen is counter-productive.) Thinking about this one. I partially have different opinions but the UI is not yet casted in stone. > (To allow more control you might permit a ProblemGroup to reference many > Problems and so hide the duplicates.) Not any time soon :) For now, one has to use Bugzilla for that. > The "All incidents" page could usefully have per-incident icons for > "identified user" blue/grey head, "has-user-comment" comment bubble. Sounds interesting. Created bug 461223. Thanks for the feedback. |