-
Suggestion
-
Resolution: Unresolved
-
41
-
1
-
At the moment Jira Service desk only allows creating one layer of Groups for Request Types;
So currently there only 2 layers - Group and Request Types inside the groups.
What is being suggested in this feature request is that there are 3 layers, so that Customers are able to nest Groups and Request Types inside upper level Groups as follows:
- is cloned from
-
- Gathering Interest
[JSDCLOUD-6103] Allow creating nested Request Types and Request Type Groups to show in customer portal
Hi Jira team,
this feature is really important to us. We want customers to be able to navigate through a menu cascade of multiple groups to the correct request type. The menu cascade should reflect our request handling logic: depending on the path through the menu cascade, users should see different request types. Using forms is not an option: forms are only relevant after having chosen a request type. When users open a form to create a request, the request type cannot be changed. We also don't want to give them all request types at once because it would be overwhelming. It also wouldn't reflect our input logic correctly.
Please consider adding nested portal groups.
Best regards
Hey Sergey!
I just voted on this 
Could you please also vote on my Feature ticket?
It would be great to have the option to select the "request type" directly from the "move issue" screen when moving issues between projects!
https://jira.atlassian.com/browse/JSDSERVER-12714
This feature is critical to allow useful reporting data to be pulled from Service Teams. The current structure is not granular enough to provide a quality customer experience and makes workflows for agents unnecessarily complicated. This is often overlooked and has been sitting here for almost 5 years with next to no action. Please transition or at least respond with an update.