Summary | Allow multi-selection |
Queue | Whups |
Type | Enhancement |
State | Rejected |
Priority | 1. Low |
Owners | |
Requester | david (at) tmv (dot) gov (dot) tw |
Created | 06/25/2008 (6221 days ago) |
Due | |
Updated | 06/27/2008 (6219 days ago) |
Assigned | |
Resolved | 06/27/2008 (6219 days ago) |
Milestone | |
Patch | No |
requiring a highly complicated UI. And tickets should never be
deleted IMO.
that there shouldn't be massive ticket deletions. Of course it makes
sense to delete individual, invalid tickets.
choose whups as help desktop,that possible to delete resolved
ticket,or will have thousand tone un-need ticket.
searching old cases. Anyway, I can see this being implemented as an
API like Chuck suggested.
requiring a highly complicated UI. And tickets should never be
deleted IMO.
choose whups as help desktop,that possible to delete resolved
ticket,or will have thousand tone un-need ticket.
requiring a highly complicated UI. And tickets should never be deleted
IMO.
the API. We should make it possible via the API, but it will
unnecessarily complicate the UI for basic use. Again, in my opinion.
more words?
these ticket. There is no any short cut to do this right now, but one
by one delete.
Allowing multi selection in search result with action like "delete
ticket","change ticket" will help much.
david
State ⇒ Feedback
more words?
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Allow multi-selection
Queue ⇒ Whups
Milestone ⇒
Patch ⇒ No
State ⇒ New