Current State:

If a request type has restrictions set in a project, a project Agent who does not have the corresponding permission will not see the option for that request type in the queue filters. This also affects JQL results (such as filtering using requestTypesInGroup function) for users who have access to the work item, but are not listed under the request raising restriction. More details on this behavior:

• Request type search does not work within JQL or Request Type system field.

• Request Type search works using “Request Type=<<REQUEST TYPE NAME>>“ after hitting Enter within the JQL.

• The JQL function “requestTypesInGroup“ does not work.

• Searches other than above mentioned function works as expected, using custom field(s), labels, etc.

• Automation rules also work as expected.

Suggested Solution

The creation restriction should not apply to viewing or querying work items (as that is handled by work item security). The users should be able to filter/search for such requests, even if they may not be allowed to create them. 

For example, If a request type must be raised only by as specific group and must then be approved by managers or IT admins, under the current logic, managers and admins would see no work items under filters because they cannot raise the request.

Workarounds

• Add all the users who must filter/search those request types to the restriction list.
  • OR
• Modify Filters to use other parameters on search, for example Custom Field or Labels