Question

It'd be really nice if there was a way to define a group of users that can then be used in a search axis. For example, I would like to do:

assignedto:programmers status:active

Which would theoretically be equivalent to

(assignedto:programmer1 OR assignedto:programmer2 OR assignedto:programmer3) AND status:active

When we've somewhere defined "programmers" as consisting of "programmer1, programmer2, and programmer3".

I found this old post but don't see that it was implemented.

https://our.fogbugz.com/default.asp?fb7beta.12.81030.2

is it possible to use groups as a search? say I have a group 'programmers', can you search assignedto:programmers?

is this function there, or a plugin?

Collin Moore

Wednesday, July 15, 2009

Hi Collin,

Not yet, but that's a cool idea. We'll definitely consider it for a future release.

Daniel Wilson [Moderator] 

Thursday, July 16, 2009

In the interim I'm thinking of adding "(Programmer)" (or something shorter) to all the programmer's names (and same for Testers, Support, and HR), but it would expand all the names a bit.

Case FC2061983

Answer 1

When group-based permissions was rewritten in FogBugz 8, the main focus was to create a better way to manage permissions for groups of uses in a particular project. I don't think we thought about the ability to search based on users in a group, but that's not a bad idea.

Once a feature request gets enough votes, we'll assign a case to it and track it internally.

Answer 2

I just finished up an implementation of a plugin for what we call 'Client Groups' where you can have any number of these things, users belong to them (mapping from Person to ClientGroup), and bugs know which client the bug is for (bugs have a Client field pointing at one of these ClientGroups). Then, when you open a new bug, it automatically populates the Client field of the bug, since you're likely the client for the issue you're bringing up.

The search axes we support are assignedtogroup:"Programmers" and client:"Programmers". The first lists all of the bugs assigned to members of the group Programmers, and the second lists all bugs whose client is "Programmers" (so like art requests from programmers, etc.).

This entire plugin only took me about a day from start to finish (including plenty of distractions throughout that time), so if you need similar functionality you might want to take a similar approach.

Answer 3

Agreed. I'd like to see work for all programmers across all projects.