Summary | pick up number for guest ,if without read permission |
Queue | Whups |
Type | Enhancement |
State | Accepted |
Priority | 1. Low |
Owners | |
Requester | david (at) tmv (dot) gov (dot) tw |
Created | 04/19/2006 (6965 days ago) |
Due | |
Updated | 09/29/2007 (6437 days ago) |
Assigned | |
Resolved | |
Milestone | |
Patch | No |
First,the ticket did not realy created into system until guest confirm
by the url or pick-up number given in the first notification.This is
for verify guest's mail address.
Second,those who can provide corrct pick-up number or url,system will
treat them as CREATOR not GUEST only for that ticket.
David
not show permissions, he will get the regular notification message and
can access the ticket through the url, but it won't show up in any bug
listings.
This won't keep any anonymous user from trying several bug number
manually though, so it's only obfuscation by hiding.
State ⇒ Feedback
One problem is that SHOW permission means you can see an object
exists, but not what it is (more or less - times for calendar events
but not titles, etc.). How would having SHOW let someone see
information about a ticket, using that understanding of SHOW?
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ pick up number for guest ,if without read permission
Queue ⇒ Whups
State ⇒ New
ticket 3630not "Read"
afterwards. On this way it is possible to *report critical content*
that should not be accessible by anyone.
message,so they can read ticket's history ,if guest just have Show and
Edit permission.