Christopher Taylor wrote: > Here's an idea ... it's free so you get what you pay for ;) > > define additional ticket types: requirement, use case > > requirement is pretty self explanitory ... > for use case, you can attach your favorite use case modeling tool's file and > (i think) you can reference attachments to a ticket in the form of a > trac-link .... if so, that should get you 80% of the way there .... > > if your requirements can be held in the original ticket field which can be > modified as needed by a user with ticket admin privs.. all follow on > comments are just that ... comments >
Also, editing the ticket description is something you can do more liberally in 0.11 because you can look at the changes as you would do for a wiki page (see http://trac.edgewall.org/ticket/2945). I think we could add a new 'TICKET_EDIT_DESCRIPTION' permission that can be used to allow non-admins to edit the description. This permission could also be used by a permission policy plugin to allow editing for some ticket types only, like "requirement" or "use case" (see http://trac.edgewall.org/ticket/3163). -- Christian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
