| Summary: | Use Bugzilla's Whiteboard field to return short messages to reporters | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Technology] EPP | Reporter: | Marcel Bruch <marcel.bruch> | ||||
| Component: | Automated Error Reporting Client (AERI) | Assignee: | Project inbox <recommenders-inbox> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | denis.roy | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Marcel Bruch
Created attachment 247491 [details]
Example feedback dialog showing some more details about the error
As I mentioned in another bug, Mylyn uses Bugzilla attachments to store context. There is also a generic "tags" field that can be used. (In reply to Denis Roy from comment #2) > As I mentioned in another bug, Mylyn uses Bugzilla attachments to store > context. There is also a generic "tags" field that can be used. Tags are only visible to the user who wrote them. The idea is that committers/QA contact may provide a description what's the problem and how to solve it which can be read by everyone. I think this makes tags not appropriate for this task. (In reply to Denis Roy from comment #2) > As I mentioned in another bug, Mylyn uses Bugzilla attachments to store > context. attachments cannot be created from within the bugzilla front-end. Creating attachments would thus require some client / management UI. I've no concrete plans for this until now but maybe some time later... At the moment I try to reuse as much of the existing infrastructure as possible. Does the whiteboard text field has a size limitation? It is a MEDIUMTEXT field, so 16M according to the docs. A string with a maximum length of 16777215 characters. (In reply to Denis Roy from comment #5) > A string with a maximum length of 16777215 characters. Should suffice. Even for the garrulous-ishest committer. Server-side now synchronizes the contents of the whiteboard field and returns its content to the user sending a report. The client needs to be update to present this information. The server-side part is done. closing. thanks for the input. |