On Thu, May 6, 2010 at 9:32 AM, Roger Oberholtzer <[email protected]> wrote: > On Thu, 2010-05-06 at 09:01 -0400, Flatfender wrote: > >> What about using something like Private Ticket plugin? [1] That way >> users will only see their tickets and or tickets they are CC'd on >> depending on how it's set up. The down side may be that your dev's may >> want to annotate tickets with comments that they don't want the end >> user to see? But that may just be an issue of training your >> developers to be more customer focused in their comments. You could >> always create a separate dev ticket and reference the customer facing >> ticket from it. > > This sounds awkward to maintain. And, if a new user arrives, he will not > be cc'd on old tickets. But they may want to see them. Maintaining a > global option by changeable properties on individual tickets seems > tricky. > > As to training the developers: is that like herding cats? In fact it is > not just what is said. We may be working on new things that we do not > want to release yet. Or other innocent things that are inappropriate for > the bug users to see or be involved in. > > Still, thanks for the pointer to private tickets. I think I can have a > different use for this. > >
I didn't say it was an ideal solution :) -- 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.
