Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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
4,462,886
Community Members
 
Community Events
176
Community Groups

Request classification

Hi all,

we need to configure the system to allow a categorization of requests based on three parameters, as in the following example:

  • Level1_1
    • Level2_1
      • Level3_1
      • Level3_2
    • Level2_2
      • Level3_3
      • Level3_4
      • Level3_5
    • Level2_3
      • Level3_6
    • Level1_2
      • Level2_4
        • Level3_7
      • ….

The allowed values of a sublevel must depend on the value of the higher level. Is there any possibility of configuring Jira this way?

2 comments

No, there is no hierarchy of request types.

The closest you could get is to have multiple portals (which means separate help-desk projects, one per portal), with each portal having a different set of request types.

Why do you think you want to do this?  One of the guiding principles of service desks is that it should be quick and easy for a customer to find help, or, when they cannot find any, raise a request for help in the right place as easily as possible.  Digging through layers of request types is not simple and leads to them raising the wrong thing.

So, what problem are you trying to solve with this idea?   There may be another way to solve it within a simple portal/request hierarchy.

Hi Nic, thanks for your reply.

The idea that led me to this approach is to classify requests in order to easily extract reports that allow the manager to identify the area that is causing the most problems (this is a specific customer need), so that he can take targeted actions to reduce the amount of requests (e.g. user training).

Can I achieve this in another way based on your experience with Jira?

Yes, you use fields as intended, asking people to enter them, or even automating them if you have a sensible rule (requests in portal 1 of types A, B, or C, and requests from portal 2 of type C or D, are all "xyz", other request types in those portals are all "abc" - that's the sort of easy classification you can automate)

Like Vincenzo likes this

There are some add-ons in the marketplace that allow you to have a hierarchy. How I do this though is I have simplified request types, but use the Severity, Impact, and Urgency fields to triage requests automatically with workflow automation by assigning a Priority.

I took priority out of my request types because users always used "Highest". Using the Impact/Urgency handled this much better. The Jira Automation is based on this priority matrix. 

priority.png

Like Vincenzo likes this

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events