[Trac] Re: Setting up customer Trac

[Noah Kantrowitz]

Jani Tiainen wrote:

Noah Kantrowitz kirjoitti:

On Jul 9, 2008, at 10:09 AM, [EMAIL PROTECTED] wrote:

On Jul 9, 8:57 am, Jani Tiainen <[EMAIL PROTECTED]> wrote:

Jason Galyon kirjoitti:

I have had several people turn down Trac (or are waiting on it) due to

no private tickets for multiple projects.
On Wed, Jul 9, 2008 at 7:59 AM, Jani Tiainen <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
   Jeroen Ruigrok van der Werven kirjoitti:

-On [20080709 12:54], Jani Tiainen ([EMAIL PROTECTED]

   <mailto:[EMAIL PROTECTED]>) wrote:

Finnish language and dates/times.

I only have a few smallish Finnish translations done, but I am

   not a native

speaker.

I've almost complete translation done, just needs to be tested is it

   sane or not...

dates/times can for now be dealt with by setting the appropriate

   LC_TIME,

but it should be a preference option soon (dependent on Babel).

   Well these are just minor issues. Main concern is to have private

    some sensitive data)

tickets so customers don't see each other issues (specially if they have

Of course since I can code if needed what it would require to make a
plugin to handle private tickets so that once entered and marked
"private" nobody else than user who entered ticket or some ticket
masters can see it.

It definitely must be invisible or inaccessible from other places -
including timeline etc.

--

Jani Tiainen

Does the PrivateTickets plugin not achieve what you want?  Since they
are required to register, with admin approval, the fact that you need
to set the permissions is not a big deal.

Right, the only thing you would need to add to PrivateTickets is make it check a custom field first to see if it should run the permission check at all (private vs. public ticket), as it is currently, all tickets are private.

This seems most promising solution so far.



So this is what I want to achieve:





Normal, most needed workflow would be something like this:

And since this is "multiproduct" (not multiproject) Trac it won't have any backlinks to our internal development tracks. It might happen vice versa, but that can be done with intertrac stuff. Setup Trac for support only (bugreports and other issues). By default user is registered on system and must be authenticated - no anonymous access. User always belongs to company. All users from certain company should be able read and modify tickets entered by users from that company. Note that support people must be able to restrict tickets to certain customer. End user enters ticket. He writes simplified data: summary, description, version and type. Ticket is restricted to private for his/her company. (Notification is sent through email to all persons from company + all support people) Support checks ticket puts it in "infoneeded", "confirmed", "workinprogress" or "closed" state. So how to handle this "restriction" stuff? In theory I could add custom field to ticket that is hidden from normal endusers that contains restrictive groups (companies). and modify private tickets to check that field too. And if there is no restrictions, it means that ticket is public...

--Noah

PriavteTickets already understands groups for this purpose (you would probably want the TICKET_VIEW_REPORTER_GROUP permission). All you need is a checkbox to mark as public vs. private.

signature.asc
Description: OpenPGP digital signature