It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

What exactly is the purpose of Project Categories???

I created some Project Categories but can't find a way where they aree of actual use in JIRA, or how they help with anything...

Any examples of these categories are used?

Our structure consists of projects for Development, Services and Support (for now). And under each of those projects we have components which are our Products.

5 answers

1 accepted

10 votes
Answer accepted

They're for grouping projects together, by however you want to group them (business unit, product, something)

It's not particularly powerful though - you can't hang permissions or schemes off them, they don't flow down on to issues, or get used in greenhopper etc. You can ask, using JQL, "all issues in category X", but that's about it really.

Because they're not a lot of practical use for config, they're not that heavily used anywhere I've been.

That's what I was thinking as well. I haven't seen any categories trace down to issues or anywhere else. Basically they can be used in JQL but not for much that matters to us.

Like Rutendo.Dingembira likes this

I'm using just to group projects. it's not powerful !

That's what I said.

Like Asegid Debebe likes this

https://jira.atlassian.com/browse/JRA-4505 Assign schemes at the Project category level


Vote for this I did! It's already being looked at actively by the development team. Please make sure to state your own use cases (provide a real word example). 

Like # people like this

I use "Project Category" to differentiate our programmes, This then feeds into my Power BI report which can filter our projects by programmes. Thus providing my organisation with an easy way to get granular data (how many issues open/closed per programme/project, etc.) in an easy format with live data. 

In our organization we Categories to group projects by Business Unit.

It helps with Filters.  Great way to 'group' projects so that a filter will (easily) apply to multiple projects:  For example, all unassigned issues across multiple projects that belong to the same category.

Instead of:  (project = Proj-A OR project = Proj-B OR project = Proj-E OR ...) AND status = unassigned

This would become:  category = Operations AND status = unassigned

Where:  Operations (category) => (Proj-A + Prod-B + Projects-E + ...)

We use project categories to group projects that share similar purposes, and therefore share issuetype, screen, workflow, etc. schemes.

Very convenient for JIRA admin role. Cheers.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

308 views 1 3
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you