Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Guidance for Product categorization and Operational categorization fields in JSD

My organization is getting ready to install Jira Service Desk (replacing another "ticketing system").  I am seeking guidance and real-life examples of how others are using the Product categorization and Operational categorization cascading fields.

I am not an ITSM or ITIL expert but I've been researching best practices for incident (and [service] request) categorization.  Here are some of the resources that I found helpful:

So how is YOUR organization using these categorization fields?  If you could start over (or do a major overhaul on the existing values), what would you do?

Note: I know how to add categorization values to these fields and create request types and the other Jira admin-type functions.  I'm seeking guidance on which values to use in each field.

Note 2: I recognize that the actual values in these fields depend on many factors.  The challenge is taking the categorization concepts and coming up with useful values.  At this point, I feel like it would be most valuable to see actual value lists that others are using.  But I'm open to other input as well.  Thanks!

1 comment

Hi Brian, 

I am currently in the same position as you.  Thank you for the resources.  Did you ever hear back from anyone with how they are doing it in the real world?



Hi @Lindsay Siurna ,

I haven't received any responses.  However, this is our v1.0 list of Product Categorization values:

  • Data
    • Data Service
    • Database
    • Extract Transform Load (ETL)
  • Documentation
    • Audit
    • Information
    • Knowledge Article
    • Report
    • Standard Operating Procedure (SOP)
    • Training
  • Hardware
    • Cell Phone
    • CPU
    • Desk phone
    • Desktop
    • Docking Station
    • Hard Drive
    • Headset
    • Keyboard
    • Laptop
    • Memory
    • Monitor
    • Mouse
    • Peripheral
    • Printer
    • Projector
    • Scanner
    • Server
    • Soft Phone
    • Surface Hub
    • Tablet
    • TV
    • Virtual Machine (VM)
    • VPN Phone
    • VTC
  • Infrastructure
    • Active Directory (AD)
    • Distributed File System (DFS)
    • DHCP
    • DNS
    • MFA
    • Permisson
    • Proxy
    • Resource Service
    • Shared Folder
    • Storage
  • Network
    • Circuit/ISP/WAN
    • Firewall
    • Load Balancer
    • Router
    • Switches
    • VPN
    • Wireless
  • Security
    • Account
    • Access
    • Badge
    • Permissions including Elevated Privileges
    • Storage
  • Software / Business Application
    • <list of apps/systems supported by our IT Service Desk>
  • Other


Our Operational Categorization field is not as well-defined right now but here is a draft:

  • Type Of Request
    • Add/Create/Provision
    • Change/Modify/Extend
    • Configure
    • Copy
    • Delete/Remove/Terminate/Decommission
    • Disable
    • Enable
    • Execute
    • Move
    • Remove
    • Repair
    • Restore
  • Alert
    • Disk Space
    • Malicious Email
    • Malware
    • Symantec
  • Break / Fix / Error
    • Data Issue
    • Error Message
    • Exception
    • Outage
    • Password
    • Process Issue
    • Slowness
  • Communication
    • Call Drop
    • Call Quality
    • Certificate
    • Dead Air
    • SSL Disconnect
    • Static Call
    • Switch Reboot
  • People Management
    • Contract to Employee
    • Department Change
    • Leave of Absence
    • Location Change
    • Manager Change
    • Multiple Changes
    • Name Change
    • Offboard
    • Onboard
    • Personal Info Update
    • Role Change
    • Security Group Change
    • Title Change
  • Other


We are open to feedback so let me know what you think.



Like # people like this

Thanks for sharing Brian.  It looks similar to what we were thinking.  How is it working for you?

@Lindsay Siurna The categorization fields seem to be working well for us so far.  We went live with Service Desk in late December so we've only been using them for a little over 2 months. 

Neither field is required but the Product Categorization has a nearly 100% use rate.  Operational Categorization has a value on about 50% of our tickets; and values are configured for several of our Request Types so it seems the use would be less than 50%.

The level of granularity seems to OK right now but I suspect we'll need to revisit and make adjustments later on.  These fields are primarily for reporting and analysis purposes so we'll have to wait and see what the data reveals at a later date. 

Unfortunately my responsibilities have shifted so I'm not as close to the data right now, so I can't give you a better answer than that.  But hopefully it was helpful!

Like # people like this

Hello Brian,


Can you help me to solve the problem statement which i have raised in community 

Here is link:

Community Discussion Link 





Log in or Sign up to comment
Community showcase
Posted in Jira Service Management

Jira Service Management Documentation Opportunities

Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...

320 views 0 10
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