Task #2081
closedImprove BZ wizard
100%
Description
mockup for first step of the wizard (which finally is the default - hallelujah!)
Files
Updated by ste ve over 8 years ago
- File LO bug wiz 1 mockup.jpg LO bug wiz 1 mockup.jpg added
Updated by ste ve over 8 years ago
Suggested changes:
TODO
13. Check the lists of frequently-reported bugs reported in the last 6 months: → no name for that, just show the bugs. It's obvious they are hot and or recent. No description is needed here.
14. quality of list of last 180 days is poor: current #1 bug is https://bugs.documentfoundation.org/show_bug.cgi?id=76239 from march 2014. so last 180 is not concerning when the bug was filed but when it was last touched. in case of this bug, tags were removed. that results in really old bugs that are already fixed ending up on this priority list which is imo plain wrong and not a good way to do it. either remove the initial bug suggestions (which at the moment I tend to recommend) or improve it - a lot).
15. if the initial list is kept, don't make it scrollable. either enlarge the window size of that frame to show more bugs or reduce number of shown
4. instead of a none descriptive headline use the action that is done. so step 1 instead would be "Please summarize your issue or request in one sentence:" followed by
5. a wider description field, so an entire sentence can be shown DONE
Step 4 + 5 are not done from what I see. I see NO HEADLINE and description field could easily be twice the width without taking up any more screen estate.
6. use summary field that offers similar bugs in real time. see: https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CFirefox how that should be done
8. don't show more than xx search results and avoid a scroll bar. The search results window should be so big that it always fits the default xx search results DONE, set it to 100 → not good imo. 100 results is overwhelming. show 25 at most.
9. adapt how mozilla presents search results (ID, Summary, Component, Stats) since that is much better than current LO implementation
10. add button to "Follow bug" for earch search result, so users can instantly cc themselves if they find a bug that matches what they were about to file
12. field for summary and "find similar issues" button should of course be above the search results and not vice versa
16. "Validate that summary is at least 4 letters" → a four character summary is basically an invalid bug. make it 15 characters at least
DONE
1. by default show hottest bugs of last 2 weeks:
* do not show name "hottest bugs of last 2 weeks" just show them
* remove option to show top 100 all time bugs, this is a bad default and irrelevant at this place
2. rename button "search" to "Find similar issues"
3. remove "Step 1 of 3 - has your bug already been reported?"
* let's not even list steps at all, instead have a clear form and be done with filing the bug
11. add button "My issue is not listed": pressing that button then leads to the next page or shows the rest of the BZ wizard to fill a new bug. by default this part should be hidden when the user arrives at the wizard
17. critical and major must not be included as options for the user to select, 2017-03-27 DONE
Updated by Xisco Fauli Tarazona over 8 years ago
- Assignee set to Xisco Fauli Tarazona
Updated by Xisco Fauli Tarazona over 8 years ago
Other changes done:
- Validate that summary is at least 4 letters
- Add version field
- Add text for attachments
- Add links to Summary, Version, Product and Component as in https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice
- Make version, actual Results and expected Results fields mandatory
- Remove superfluous text
- Rework layout of the comment created when the bug is filled
Updated by Beluga Beluga almost 8 years ago
I tested with a regular user and I was shown the severities Critical and Major, even though these are not allowed to be used. I hope they could somehow be removed from the form, easier than from the "normal" interface itself.
Updated by Xisco Fauli Tarazona almost 8 years ago
Critical and Major options removed in https://bugzilla-test.documentfoundation.org/enter_bug.cgi?product=LibreOffice&format=guided
Updated by Florian Effenberger over 7 years ago
What's the status of this? Pending? Deployed? Who's wearing the hat? Then we can categorize this ticket accordingly.
I'm wearing the hat here. I've done some work in bugzilla-test but it's not finished yet. I'll move it to production once it's done
Updated by Xisco Fauli Tarazona over 7 years ago
Work done in https://bugzilla-test.documentfoundation.org/enter_bug.cgi?product=LibreOffice&format=guided. Asking cloph to move it to production...
Updated by Xisco Fauli Tarazona about 7 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Updated by Florian Effenberger about 7 years ago
Xisco Fauli Tarazona wrote:
Work done in https://bugzilla-test.documentfoundation.org/enter_bug.cgi?product=LibreOffice&format=guided. Asking cloph to move it to production...
Has this happened?
Updated by Xisco Fauli Tarazona about 7 years ago
Florian Effenberger wrote:
Xisco Fauli Tarazona wrote:
Work done in https://bugzilla-test.documentfoundation.org/enter_bug.cgi?product=LibreOffice&format=guided. Asking cloph to move it to production...
Has this happened?
Yes, the ticket is Resolved now
Updated by Florian Effenberger about 7 years ago
- Status changed from Resolved to Closed