So I installed CondField, restarted Apache, and when I create a new ticket the Ticket Properties area is empty. Thoughts? Chris
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Deen Sethanandha Sent: Tuesday, June 05, 2007 3:22 AM To: [email protected] Subject: [Trac] Re: Organizational Approach with Tickets Chris, I also have similar situation. Ticket has many attributes priority, severity, status, components. Priority, Severity, and component can be changed easily using drop-down list. However, status is tided with workflow. It changed based on action performed to the ticket. I think CondField plugin only handle drop-down list. I think it's great plug-in and we can count on Noah. At the moment, Trac handled only one set of action. You can use custom workflow to change it. I also like to see someone creating plugin that customizs workflow based on ticket type. It is on my to do list but I don't think I will get to it untill I finish what I am working on. Here is a work around. If you use a custom work flow, you could change name and number of status. However, you can only have one set. If you decide to use the default workflow you need to map ticket status and what it means yourself. If status is New for task, it mean "open". If status is Assigned for Task, it means "in-progress". If status is Fixed, it means "recommend closure". if status is "Later", it means "on-hold". If status is "Close", it means closed. We could do similar thing to enhancement as well. Another alternative is to have custom field that allows you to specify status manually regardless of actual ticket status and then use CondField to change the list based on ticket type. If the bug status is not user friendly enough, you could change it to more generic term as you mention for task. I really like Trac since it enables you to be creative. On 6/4/07, Noah Kantrowitz <[EMAIL PROTECTED]> wrote: Wetterman, Christopher wrote: > All, > > I'm working on configuring our install of Trac for tasks and bugs > (defects). Are both tasks and bugs priorities tagged the same? That is > with current settings tasks could be labeled as trivial, minor, major, > etc.... As I'm accustomed to tasks can be open, in progress, on hold, > recommend closure, and closed. How would your approach be to this? > Currently, via WebAdmin, I have created the following priorities: > > task-open > task-in progress > task-on hold > task-recommend closure > task-closed > bug-blocker > bug-critical > bug-major > bug-minor > bug-trivial > bug-cosmetic > > The thing to remember, which isn't difficult, is when assigning a task > to choose a task priority and not a bug priority. I had this natural > assumption that when choosing a task the priority options would update > on the fly and only task priorities would be available. Same goes with > bugs and enhancements. If Trac doesn't distinguish like this is there a > mod or plug-in available that does such? See the CondFields plugin on trac-hacks. --Noah --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
