Version 6 (modified by deyan, 16 years ago) (diff) |
---|
Analysis
Overview
As we are getting close to beta versions, issue tracker should be set up in a way that is convinient for the end users to report bugs.
Task requirements
- Review trac permissions
- unregistered (anonymous) users should be able to:
- Create a ticket of type bug
- An explanation of what should they fill in will be useful
- unregistered users should NOT be able to
- Create more than number of tickets for a time interval
- Delete or edit existing tickets - this should also be noted (this one is easy - ticket deletion is not possible without a plugin).
- Some of the registered users should be able to
- Delete tickets - this should be discussed - accidently deleting of tickets won't be nice, but unwanted content should be deleteable. Probably deletion of bug tickets only is enough, but should be done by some users only.
Task result
Issue tracker ready for anonymous bug reporting.
Implementation idea
Install the plugins from the Related section.
Related
- http://trac-hacks.org/wiki/TicketSubmitPolicyPlugin allows some fields to be required for posting a ticket.
- http://trac-hacks.org/wiki/TypedTicketWorkflowPlugin can modify the task depending on task type
- http://trac-hacks.org/wiki/TicketDeletePlugin allows deleting of tickets. Currently, we may not need this but having a way to deal with unwanted content is good.
- http://trac.edgewall.org/wiki/SpamFilter spam filter may come handy, but ip blocking may block our local ip-s too.
How to demo
(Provide instructions for demonstration of the task.)
Design
(Describe your design here.)
Implementation
(Describe and link the implementation results here (from the wiki or the repository).)
Testing
(Place the testing results here.)
Comments
(Write comments for this or later revisions here.)