Differentiating Project types in JQL.

[Radia Dev]

Hi Community,

I hope you are having a productive week.

I am reaching out for assistance with a specific JQL challenge related to dashboard reporting:

The Challenge: Duplicate Statuses in Two-Dimensional Filter

We are using a single JQL query that pulls tickets from over 150 projects. When this JQL is applied to a Two-Dimensional Filter, we are seeing duplicate Status columns (e.g., "In Progress" appears twice). This behavior is confirmed to be caused by the query combining both Company-Managed and Team-Managed (or People-Managed) project types.

The Request: Efficient Project Type Identification

Given the large number of projects (150+), manually checking each project's type is highly inefficient.

Can anyone suggest a JQL function, an API endpoint, or any quick method/shortcut to efficiently differentiate or list the projects by type (Company-Managed vs. Team-Managed) without having to inspect them one-by-one?

Any advice on solving this bifurcation problem would be greatly appreciated!

Thank you for your collective expertise.

Best regards,

Dev Radia.

[Marc -Devoteam- · Accepted solution]

Hi @Radia Dev 

You can JQL on projecttype, but here you can differentiate between business, software, service_desk, ...

There are no JQL options for Team or Company managed.

Via the API you can use api-rest-api-3-project-projectidorkey-get (this is per project), see the "style" parameter.

This will show classic or next-gen, this specifies Company or Team managed.

[Radia Dev]

Hi @Marc -Devoteam- ,

Thank you for your help!

This will definitely help! I can write code to run this across all 150 projects and collect the data!

Thanks,

Dev Radia | Senior Technical Support Engineer

📧 radia.dev@pens.com | 🌐 https://www.pens.com/

[Marc -Devoteam-]

HI @Radia Dev 

Please accept my answer as a solution, if my answer helped to solve or provide a workaround to your request.

This will help other community member trying to solve the same or provide them with a work around

P.S. If the answer is very valuable to you, please share some kudos.

[Radia Dev]

Hi @Marc -Devoteam- ,

Thanks for reminding me! I have accepted Answer!

Thanks,

Dev Radia.

[Marlene Kegel - codefortynine]

Hello @Radia Dev,

Glad to hear you were able to solve the issue.

For anyone else reading along, another option is to use an app such as Quick Filters for Jira Dashboards (full disclosure: I’m the product manager).

The app matches statuses by name, not by ID. This means that if work items use the same status name, they are treated consistently across all gadgets.

You can explore Quick Filters for Jira Dashboards on the demo dashboards without installing it. The app makes dashboards filterable, which can be helpful when working with cross-project dashboards or when you want to avoid maintaining multiple dashboards. It also supports statistics for Jira number fields, for example to track estimates or story points.