Edgewall Software

Ticket #6059 (closed task: fixed)

Opened 16 months ago

Last modified 2 months ago

Add stricter user guidelines for creating new tickets on t.e.o

Reported by: anonymous Owned by: jonas
Priority: normal Milestone: not applicable
Component: project Version:
Severity: normal Keywords:
Cc:

Description (last modified by cboos) (diff)

Developers aren't happy with the user testing and the whatnot

Attachments

Change History

follow-up: ↓ 2   Changed 16 months ago by cboos

  • keywords tobedeleted added
  • status changed from new to closed
  • resolution set to invalid

Looks like we have a record number of test tickets today...

Argh...

THIS IS NOT A TEST SYSTEM

in reply to: ↑ 1   Changed 16 months ago by eblot

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...

  Changed 16 months ago by cboos

  • status changed from closed to reopened
  • description modified (diff)
  • type changed from defect to task
  • component changed from general to project
  • summary changed from I want to report something to Add stricter user guidelines for creating new tickets on t.e.o
  • milestone set to 0.11
  • keywords tobedeleted removed
  • resolution invalid deleted

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:

  Changed 16 months ago by r.blum@…

So why is this a pending bug for 0.11 - shouldn't this be post 0.11?

  Changed 16 months ago by cboos

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.

follow-up: ↓ 8   Changed 13 months ago by anonymous

What does t.e.o. mean?

  Changed 13 months ago by philbar

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.

in reply to: ↑ 6   Changed 13 months ago by eblot

Replying to anonymous:

What does t.e.o. mean?

trac.edgewall.org

  Changed 11 months ago by cboos

  • milestone changed from 0.11 to not applicable

Well, maybe one day. Apparently neither cmlenz nor jonas are interested in doing this :-(

  Changed 2 months ago by cboos

  • status changed from reopened to closed
  • resolution set to fixed

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 :-)

Add/Change #6059 (Add stricter user guidelines for creating new tickets on t.e.o)

Author



Change Properties
<Author field>
Action
as closed
Next status will be 'reopened'
to The owner will change from jonas. Next status will be 'closed'
 
Note: See TracTickets for help on using tickets.