improved user groups

[_mips_]

Hi there, first thank you for making Trac, it helps us a lot in managing all the tasks and tickets at works. Now the problem we have is with managing groups of users. We have some teams that have sub-group assigned to specific tasks and with the actual support for groups our reports or queries are real nightmares.

So my question is : could it be possible to add a better user group management in Trac ? IMHO, this feature would help a lot in professional environment where we don't have only one dev team like in opensource projects.

Greetings, Damien

[Noah Kantrowitz]

Trac supports hierarchical groups just fine.

[anonymous]

Is there a way that the TRAC hierarchical groups could be integrated with an htgroups file, in a manner similar to the way that TRAC user accounts are integrated with an htpasswd file? This would allow us to manipulate groups consistently between our webserver and the trac accounts. (At least, that's how I interpreted the question originally posted).

[ebray]

See ​th:HtgroupsPlugin.

[anonymous]

Ok maybe i must explain a bit more.

We have a team called 'main', but in terms of task this team has some sub-teams where one member of the main team can be member of one or more sub-teams. So yes, i've been able to create teams and sub-teams without problems.

No what i want to do, is to make some supervisor reports. For example, i want a team leader to be able to see all the opened tickets of all the teams he is member. This means the tickets assigned directly to the groups or indirectly to a member of those groups.

What i tried was :

SELECT p.value AS __color__,
 owner AS __group__,
 id AS ticket,
 summary,
 component,
 milestone,
 t.type AS type,
 priority,
 time AS created,
 c.value AS 'échéance',
 description AS _description
FROM
 ticket t
LEFT JOIN enum p ON p.name = t.priority AND p.type = 'priority'
LEFT JOIN permission pe ON pe.username = $USER AND pe.action = LOWER(pe.action)
LEFT JOIN ticket_custom c ON t.id = c.ticket AND c.name = 'echeance'
WHERE
 (status = 'accepted' OR status = 'assigned')
 AND (owner = pe.action OR pe.username = $USER)
ORDER BY
 __group__,
 substr(c.value,7,4), substr(c.value,4,2), substr(c.value,1,2),
 t.priority,
 p.value,
 milestone,
 t.type

But it does not work.

[anonymous]

I forgot to tell that the problem i got was duplicates. Actually on my environment i got 3 times the same ticket.

Thanks, Damien

[ebray]

Please stop asking what are essentially support questions in tickets. Your problem with the query is almost completely unrelated to your original issue. And the problem is probably with your SQL—the JOIN on permission will return a row for each group the user belongs to. A GROUP BY t.id might solve that. Furthermore, a better way to check if an action is a group might be pe.action LIKE '@%' or somesuch.

Finally, Trac doesn't really support assigning tickets to groups like you're doing, though I suppose what you're doing is workable. Better support for this would be nice, but I think that's essentially covered by #2662. At this point it would probably also be possible to write a plugin to provide better support for assigning tickets to groups.

[shendric@…]

The comment "See ​th:HtgroupsPlugin." Addressed my concerns. Thanks for the response — I should have found that myself.