JIRA Service Desk - Operational/Product Categorisation


I am just in the process of setting up our JIRA Service Desk instance. We have a defined Categorisation model that we would like to set up in the tool allowing for us to track issues by either technology or products specific to our organisation.

The best way to do this seems to be by amending the Product and Operational Categorisation fields to contain this information for us. I am guessing that this is a common ask by different companies to allow them to report on products specific to their own architecture and service maps. Can anyone advise on the best way to amend this data?

Our categorisation information is not so large that I would necessarily need to import this but I cannot find a way to amend this manually either, and cannot find any queries about this on here to try at fixes. Any assistance would be gratefully received.


3 answers

0 votes
Ivan Tovbin Community Champion Jan 06, 2018

Hi Gareth,

If I understood your requirement correctly, then components might be the solution you are looking for.

Hi Ivan,

Thanks for your response. Components may give us some of the functionality we are looking for, so thank you for that.

However, we would still need to amend the entries for the Product and Operational Categorisation to match our reporting needs. Are you able to advise as to how this is most easily done?

As I mentioned initially, if this has to be done manually (rather than in bulk), that is not much of an overhead for us. We just want to be able to enhance our reporting and would need different parameters than are currently available to allow us to do this.


I have managed to work out how to do this now, so no need to provide any further guidance at this time.



One final question, Ivan...


The below issue has been open since 2005 and without any update since 2016. Do you know if this is actively being worked on? (It shows as being unassigned)


Our reporting structure is based around this functionality being in place.



As it's unassigned and inactive, I'm afraid Atlassian are not working on it.  Open does mean they have not ruled it out though.  And I know they're working on revising the way fields are attached to projects in general.

Thanks for such a prompt response, Nic. It does seem like a pretty simple ask and one which would bring great benefits, given the number of people who have voted on this issue. I shall continue watching the issue for any updates that may come along.

Suggest an answer

Log in or Sign up to answer
Community showcase
Asked Dec 06, 2018 in Jira Service Desk

Looking for teams who switched from email to Jira Service Desk

The Jira Service Desk marketing team is working on a guide to help new Atlassian customers switch from email to JSD and we'd love to hear from you! Please share: - What made you realize that i...

740 views 6 10
View question

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you