How can I group project categories?

[Petra Rumlová]

For my purpose, I need something like at least 2-level categories or ability to add more categories. Is there any way how to solve this?

[Jack Brickey · Accepted solution]

there is a bit of missing info here...what do you want to be able to do w/ these categories? Can you provide an example of your use-case?

I assume you know of the currently available Project Category? This field is basically a label/tag you can apply to any project and in the Project page you can filter on the field. I use for labeling Archived projects and things like what business unit it falls into. However, there isn't the ability to have a second category field per project. You could add an issue custom field and you could make it a drop down and per project use a post function or automation to fill it in per project so that every issue in a specific project had the same value. Not sure that is what you are wanting though.

[Petra Rumlová]

Thanks for your answer, I'll try to give you more info.. Some  of our Jira projects already have Categories (but not most of them). New requirement is, group them by "internal", "external".

Current situation example:

Projects: [Project1, Project2, Project3, Project4, CustomerName1, CustomerName2, ProjectXYZ]

Categories: [CustomerName1]

{ CustomerName1: { projects: [Project4, CustomerName1] } }

{ SomeCategory: { projects: [Project1, ProjectXYZ] } }

(rest of projects without category)

Desired situation:

{ CustomerName1: { projects: [Project3, Project4, CustomerName1] } }

{ SomeCategory: { projects: [Project1, ProjectXYZ] } }

{ Internal: { projects: [Project1,Project2,ProjectXYZ] } }

{ External: { projects: [Project3, Project4, CustomerName1, CustomerName2] } }

or

{ External: { projectCategories: [ CustomerName1, CustomerName2 ] } }

[Jack Brickey]

i assume you want a queryable solution. If not you could use the description. But I expect you do so would point you to search the Marketplace but I don't know of any such addon personally.

[Petra Rumlová]

Yes, I need queryable solution. For now, your second advice with custom fields seems like the best solution. Thank you!

[Petra Rumlová]

@Jack BrickeyCan you give me an advice, where could I find some guides for automation rules for adding field with chosen value, please? I tried to find it, but not sucessfully. Thanks

[Jack Brickey]

So first you need to create a custom field. I assume you don’t need help with that but correct me if I am wrong. Then the automation would be something like this...

trigger = issue created

conditions = whatever makes sense for your situation. If you want the value set on every issue then simply leave conditions off.

action = edit issue ...choose the new custom field and specify the value.

you can create this rule in every project where you want to specify the category.

[Petra Rumlová]

Yes, I don't need help with custom field creation :).

Thanks for your answer.

Is there any way, how to do this via API?

Use case: I have about 196 projects, I have a table with names and desired values of custom fields. So my idea is, set custom fields value for them programatically. Only what i found is, how to set that value to issue using REST API, it's easy but it doesn't solve my problem for new issues.

[Alexey Dorofeyev]

Hi @Petra Rumlová 

You can use Project Groups for Jira add-on for this

https://marketplace.atlassian.com/apps/1216998/project-groups-for-jira?hosting=server&tab=overview

[Niranjan]

Hi @Petra Rumlová 

JIRA allows defining only one category for each project. I would recommend that you follow a naming a convention that helps you to categorize it as required.

For example, if you can create a category AB, then the projects under AB can be 

A-Project1

B-Project2