Opened 17 years ago
Closed 16 years ago
#6059 closed task (fixed)
Add stricter user guidelines for creating new tickets on t.e.o
Reported by: | anonymous | Owned by: | Jonas Borgström |
---|---|---|---|
Priority: | normal | Milestone: | not applicable |
Component: | project | Version: | |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
Developers aren't happy with the user testing and the whatnot
Attachments (0)
Change History (10)
follow-up: 2 comment:1 by , 17 years ago
Keywords: | tobedeleted added |
---|---|
Resolution: | → invalid |
Status: | new → closed |
comment:2 by , 17 years ago
Replying to cboos:
Looks like we have a record number of test tickets today…
Argh…
THIS IS NOT A TEST SYSTEM
Maybe t.e.o. needs a special Trac plugin that pops up a confirmation request when the description is less than 2 line long (typical length for 'test' tickets), as it appears that people don't read the static red box…
comment:3 by , 17 years ago
Component: | general → project |
---|---|
Description: | modified (diff) |
Keywords: | tobedeleted removed |
Milestone: | → 0.11 |
Resolution: | invalid |
Status: | closed → reopened |
Summary: | I want to report something → Add stricter user guidelines for creating new tickets on t.e.o |
Type: | defect → task |
Well, as soon as we have 0.11 here, we could make the New Ticket link point to NewTicketGuidelines (or a more lightweight version of it), using a TracNavigation redirection. We could then add a few predefined /newticket links there, like:
- if you're using 0.10.4 create a ticket for 0.10.4
- if you're using a development version of 0.11 create a ticket for 0.11
- in other situations, don't forget to set the version information yourself
comment:5 by , 17 years ago
It's a task for the project. We usually run a pre-version of a release before actually making the release (#4315) and once this will be the case for 0.11, it should be possible to complete this task.
comment:7 by , 17 years ago
I second the idea about the conformation screen.
There seems to be too many valuable resources devoted to fixing this problem. Someone should make a simple plugin that asks for a conformation, with a disclaimer, prior to submitting a ticket for any thing and anyone that hasn't logged into the site.
comment:9 by , 17 years ago
Milestone: | 0.11 → not applicable |
---|
Well, maybe one day. Apparently neither cmlenz nor jonas are interested in doing this :-(
comment:10 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
That actually happened a few months ago, the "New Ticket" navigation button now leads to the NewTicket page and the number of dumb test tickets dropped a lot :-)
Looks like we have a record number of test tickets today…
Argh…
THIS IS NOT A TEST SYSTEM