Filtering on Topic Groups

[AnthonyIm]

Hi Everyone, I have run into a wall for something I thought was going to be very easy. I have a request queue that has two Topic Groups (Regular Studio Requests and Express Lane Requests). Each Topic Group has different Queue Topics which have different custom forms and routing rules. It is working great! I want to build a report that shows all the Express Lane Requests. However, there is nothing in an issue report that links to a Topic Group. I was able to display the column by doing queueTopic:parentTopicGroup:name but cannot figure out at all how to do a filter. Unfortunately I cannot use Queue Topics because there are some Queue Topics that are shared (i.e. there are two PDF Request Queue Topics, one with a Topic Group of Regular and the other with Express). Any ideas how to do this? Thank you, Anthony

[NRYNR]

Hi Anthony, here's how it's done. Keep in mind that this filter will only capture issues with queue topics one level down from the topic group. If you have nested groups, the issues will not be included. To add the additional nested groups and their queue topics, add the IDs with a tab separator. Filter: queueTopic:parentTopicGroupID=57d80cd7007eb942bbb8cd974e6a1256 queueTopic:parentTopicGroup_Mod=in Grouping: group.0.displayname=Topic Group group.0.linkedname=direct group.0.namekey=name group.0.valuefield=parentTopicGroup:name group.0.valueformat=string textmode=true

[AnthonyIm]

Thank you! I guess there isn't a way to reference the name in the filter for them. Luckily I only have two Topic Groups so getting the IDs is not difficult.

[Kelly_Wehrmann]

Thanks for sharing the filtering tip. However, the idea of text mode code still proves daunting to basic report users, as a result we have yet to venture down the path of layered queue topics. Don't get me wrong, it's a nice feature, but like a few other features if you can't easily report on it, we steer clear of it, if possible. :)

[NRYNR]

You can always add the Topic Group to a custom form on the issues. Then it becomes a field available to the users in the standard reporting interface.

[AnthonyIm]

Actually, this is a really good idea if you need to filter Queue Topics by name. Because every queue topic on every project has its own unique ID, when I tried to do a report combining two of them, I couldn't get it to work. Luckily they both had their own custom form so I just filtered on Category. But if I had a calculated field on the custom form for Queue Topic Name, I could have done that. Great idea Narayan!

[NRYNR]

Anthony, thank you for sharing your thoughts on this. I too have often had to rely on the ID in filters, but this would eliminate that need.