#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: |
----------------------------------------+-----------------------------------
Changes (by [EMAIL PROTECTED]):
* keywords: review =>
Comment:
![Clearing 'review' keyword, as the patch it applied to has been
committed]
A significant subset of the recent discussion has been only peripherally
related to the subject of this ticket, leading to a very long string of
comments that don't have much bearing on fixing this defect. I would like
to suggest that any further debate on authentication philosophy take place
elsewhere, perhaps on a mailing list, or at least in another ticket. I
will attempt to summarize current status, so that there is a concise
statement of what action remains to be taken regarding this ticket.
== Summary of ticket status at this point ==
TracDev/Proposals/Journaling (IMO) outlines the correct long-term goal,
and it may be appropriate to file an 'implement that proposal' ticket at
some future point.
In the shorter term, to resolve this ticket, and as a stepping stone on
the path to implementing that proposal, I think we should add
`is_authenticated` fields alongside every current `author` or `reporter`
field (in the same tables), and arrange for that information to be set and
displayed as appropriate.
This will allow work to proceed in making the wiki and ticket subsystems
collect, store, display, and use the `is_authenticated` information
immediately, to get this ticket fixed for milestone:0.11.
This is in no way a step in a different direction to the journalling
proposal, rather it is a preparatory step to make it easier to implement
in the future: when the time comes to implement it, that work will be
aided if all the disparate subsystems are already handling all the
relevant fields, and it is only the database interaction code that needs
changes, rather than the processing and display logic too.
--
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
