---

anonymous claiming to be kkinnell added on 2008-11-26 15:43:38:
I made that way too hard. There isn't any need to know anything but the login. You can just add

    set comment "<i>[htmlize $login] posted on [date]<i><br>\n$comment"

above the submit_ticket command.

---

kejoki added on 2008-11-25 20:01:53:
and now I ./reference.wiki now cut that out! append and preview...

---

kejoki added on 2008-11-25 19:54:17:
big test

• just checking

hoo boy.

---

kkinnell added on 2008-11-25 18:06:41:
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

<th1>
  if {[info exists submit]} {
     set status Open
     submit_ticket
  }
</th1>

If you change that to

<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

$comment"
     submit_ticket
  }
</th1>

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.

---

kkinnell added on 2008-11-25 18:04:24:
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

<th1> if {info exists submit} { set status Open submit_ticket } </th1>

If you change that to

<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

$comment" submit_ticket } </th1>

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.

---

anonymous added on 2008-11-24 20:56:32:
Yes, it would be nice to have it on the "View Ticket" page (tktview).

---

eric added on 2008-11-24 15:36:00:
The userid is available in the ticket history page, do you need more than that?

---

anonymous added on 2008-11-24 14:58:24:
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.

---

drh added on 2008-11-23 12:00:39:
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.