Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

What is a good report to identify all the Request Queues?

Avatar

Level 2

Hello,

I have just taken over as Admin for this company's WF. Previously request queues were made but were not identified as such by the custom status. I am trying to make a report to see all projects acting as request queues but all the filters I have tried bring back nothing or too many. Anyone have a good solution?

1 Accepted Solution

Avatar

Correct answer by
Level 9
Level 9

There are two kinds of projects that can be considered "Request Queues" 
1. A project that is published as a queue and its name appears in the dropdown menu under "Request Type" after the user clicks the blue "Submit Request" button on the Requests landing page.
2. Sometimes, a project from #1 above will route requests to a different intake project that has limited access. Users ofter refer to these projects as queues also.

To pinpoint projects that fall into category 1 above (my personal nomenclature for these is "routing project"), you can use the "Published Queues" filter shown in the below screen capture. 

Published Queue Filter.png







To identify projects that fall into category 2 above (my personal nomenclature for these is "landing project"), you can use the below text mode:

EXISTS:a:$$EXISTSMOD=EXISTS
EXISTS:a:$$OBJCODE=RRUL
EXISTS:a:defaultProjectID=FIELD:ID
statusEquatesWith=CUR	PLN
statusEquatesWith_Mod=in

View solution in original post

6 Replies

Avatar

Level 4

I put all of our projects that are set as request queues into a portfolio titled "Request Queues." Maybe that would help you as well.

Avatar

Level 2

That would be helpful, but first I am trying to find them all! Most appear to be located within the departmental portfolios, but I want to make sure I am not overlooking any.  Once I do find them all I will put a Project status of "Request Queue" on them.

Avatar

Correct answer by
Level 9
Level 9

There are two kinds of projects that can be considered "Request Queues" 
1. A project that is published as a queue and its name appears in the dropdown menu under "Request Type" after the user clicks the blue "Submit Request" button on the Requests landing page.
2. Sometimes, a project from #1 above will route requests to a different intake project that has limited access. Users ofter refer to these projects as queues also.

To pinpoint projects that fall into category 1 above (my personal nomenclature for these is "routing project"), you can use the "Published Queues" filter shown in the below screen capture. 

Published Queue Filter.png







To identify projects that fall into category 2 above (my personal nomenclature for these is "landing project"), you can use the below text mode:

EXISTS:a:$$EXISTSMOD=EXISTS
EXISTS:a:$$OBJCODE=RRUL
EXISTS:a:defaultProjectID=FIELD:ID
statusEquatesWith=CUR	PLN
statusEquatesWith_Mod=in

Avatar

Level 2

Thank you for these tips! I ended up finding very similar reports to both in the System Admin blueprint package of reports. One question, that customized filter for Published Queues-  You did that AFTER the report creation, correct? When you view the report you chose to filter and "create new filter"?  I don't see a Published Queues option in the filter abilities. Is this due to the type of report, whether it is a Project report or Queue report? I think I have what I need but its good to have all possible tools available!

Avatar

Level 9
Level 9

Ah. The example I shared is meant to be used with a Project report. (I often forget that Queue reports exist and go straight to Project reports.)

"Published Queues" is just the name I gave to a project filter. You can create the same filter directly on a Project report, but one best practice is to build your filters/views/groupings when looking at a list of projects, issues, users, etc. and then when making your report, just apply the f/v/g that you previously made. This makes it easier to apply those attributes to other reports in the future; or quickly apply changes to multiple reports that may share the same f/v/g.

Avatar

Level 2

Good idea!  I've been out of the WF ecosystem for over a year and I'm finding I need to relearn a lot of old practices along with many new ones! Totally forgot about the ability to create custom filters to apply to existing reports for a minute.