Changes to ticket 70dd027135
By kkinnell on 2008-11-25 18:09:41. See also: artifact content, and ticket history
- Change comment to "When viewing a ticket, it would be helpful to know who opened the ticket, similar to the way you can see who added additional comments. <hr><i>drh added on 2008-11-23 12:00:39:</i><br> The "Contact" field contains that information, if I understand you correctly. But the information is an email address. Many people prefer to keep their email addresses private (to minimize spam, I suppose) and so that Contact field is not shown unless you are logged in as a user that has the "e" privilege. To help prevent exposure of email addresses, SQLite does not store the email address in the artifacts that comprise the ticket. Instead, it stores a SHA1 hash of the email address. A separate database table (the CONCEALED table) stores a translation from SHA1 hash back to email address. The CONCEALED table is not transferred on a "clone" or "sync". You can get a copy of the CONCEALED table by doing: fossil config pull email But that will only work if the person doing the pulling has the "e" privilege set. <hr><i>anonymous added on 2008-11-24 14:58:24:</i><br> I was actually referring to the logged in name of the user who reported, not the email address. I agree that that should not be displayed. For example, this ticket should say "anonymous" since I do not have a login on this system. The reason I requested this: in my company, only the person who opened a bug may close it, the person who fixed it marks it "fixed". It is helpful to know at a glance who opened a ticket. <hr><i>eric added on 2008-11-24 15:36:00:</i><br> The userid is available in the ticket history page, do you need more than that? <hr><i>anonymous added on 2008-11-24 20:56:32:</i><br> Yes, it would be nice to have it on the "View Ticket" page (tktview). <hr><i>kkinnell added on 2008-11-25 18:06:41:</i><br> You can deal with this by changing your New Ticket HTML. Setup->Tickets->New Ticket Page The text edit has a copy of the html+th1 code for doing new tickets, at the very top is <nowiki><pre> <th1> if {[info exists submit]} { set status Open submit_ticket } </th1> </pre></nowiki> If you change that to <nowiki><pre> <th1> if {![info exists username]} {set username $login} set pstr "[htmlize $login]" if {$username ne $login} { set pstr "$pstr claiming to be [htmlize $username]" } set pstr "$pstr posted on [date]" if {[info exists submit]} { set status Open set comment "$pstr<br><br>$comment" submit_ticket } </th1> </pre></nowiki> You'll get 'so & so posted on somewhen' at the very top of the first comment in a ticket. Caveat: I haven't tested this quite as extensively as I might... Th1 isn't documented much—yet—but it's basically specialized Tcl. You can do quite a bit of customization with it, including changing sqlite tables to suit you."