#1890: Can create tickets anonymously using the username of an authenticated
user
----------------------------------------+-----------------------------------
Reporter: [EMAIL PROTECTED] | Owner: cboos
Type: defect | Status: new
Priority: normal | Milestone: 0.11
Component: general | Version: 0.8.4
Severity: normal | Resolution:
Keywords: review |
----------------------------------------+-----------------------------------
Comment (by [EMAIL PROTECTED]):
Replying to [comment:46 cboos]:
> About the `authenticated` column:
>
> See a TracDev/JournalingProposal#Asolution
Your note on this ticket seems to imply that `is_authenticated` would live
in one of the ''n'' `ticket_change` (or `property_change`, in the
generalized case) records associated with the `ticket_transaction` (or
`journal`), but the linked page (actually TracDev/Proposals/Journaling)
puts `is_authenticated` in the `journal` table. I prefer it in the
`journal` table.
If this is where `is_authenticated` is going to live, it really needs to
be handled for the generalized case, though. We don't just need to know
"who did this" for tickets. It's useful for everything.
I'm also not familiar with Trac's db schema enough to know how
straightforward it would be to tie the `journal` record to a specific
version of an item. Doing so would be necessary, of course, to actually
present this data back to the client at pageview. If this is an obvious,
simple SQL call, forgive my ignorance. If it's non-trivial, i'd be
interested in seeing a proposal for how to extract the `is_authenticated`
flag for, say, each comment in a ticket.
--
Ticket URL: <http://projects.edgewall.com/trac/ticket/1890>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
