Opened 9 years ago
Closed 8 years ago
#12295 closed enhancement (fixed)
Prevent users to create defect tickets without status report
Reported by: | Don-vip | Owned by: | stoecker |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Trac | Version: | |
Keywords: | Cc: | stoecker, simon04, bastiK, Klumbumbus |
Description
I'm tired of people who ignore the flashy, yellow, translated, instructions on newticket.
Is there a way with Trac to detect missing status reports to force users to use the "Help => Report bug" feature?
Attachments (0)
Change History (9)
comment:1 by , 9 years ago
Cc: | added |
---|
comment:2 by , 9 years ago
comment:3 by , 9 years ago
Can we pre-fill the following content in newticket?
==== What steps will reproduce the problem? 1. 2. 3. ==== What is the expected result? ==== What happens instead? ==== Please provide any additional information below. Attach a screenshot if possible.
comment:4 by , 9 years ago
Or what about changing the link in the Trac menu to https://josm.openstreetmap.de/josmticket?gdata=Cg== – this fills in the template from comment:3 automatically? :)
comment:5 by , 9 years ago
Anyway, only allowing to file bug reports with the "report bug" button is a bad idea. A moment ago, I wanted to file a bug report that way, but my JOSM (r9329) freezes when I click "report bug" in the menu bar (I'll soon file a separate bug report for this issue and the one I originally wanted to report).
But prefilling any new tickets created with the "new ticket" button on the website is indeed a very good idea.
follow-up: 7 comment:6 by , 8 years ago
I found no useful way to change the link or prefill the ticket. I think we will survive the troublesome reports. Maybe We should add a [[BadReport]] macro, so we don't need to retype the same text always? :-)
comment:7 by , 8 years ago
Replying to stoecker:
Maybe We should add a [[BadReport]] macro, so we don't need to retype the same text always? :-)
That's a good idea! :)
comment:8 by , 8 years ago
Ok. Here it is (change text at BadReport page).
---
Thanks for your report, however your ticket is incomplete and therefore not helpful in its current form.
Please add all needed information according to this list:
- The required parts of the Status Report from your JOSM.
- Please, use Report Bug from Help menu and copy & paste.
- Describe what behaviour you expected.
- Describe what did happen instead.
- Describe if and how the issue is reproducible.
- Add any relevant information like error messages or screenshots.
To ensure that all technical relevant information is contained, create new tickets by clicking in JOSMs Main Menu on Help → Report Bug.
Remember: This is a generic notice so we don't need to write the same stuff again and again. It may only apply in parts to the specific case!
---
comment:9 by , 8 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
That's something we need to endure. There are two choices
For JOSM the choice was number 1. That has drawbacks for sure, but the opposite is worse. I e.g. don't report many bugs in other bugtrackers, as usually you need to get and verify an account click there, do that, fill that check that.... When I finally reach the target I lost all interest to report a bug.
For JOSM server the design choice was to have an entrance level as small as possible.