-
Suggestion
-
Resolution: Unresolved
-
None
-
53
-
Problem description
When a field added in tab from screen configuration, and at the same it's added in "Request Form", then this field won't be shown in the tab as configured. Here are the steps:
- In screen configuration, add a new tab (let's name it with "Bear") and add a field (let's call it "Test")
- In project settings > Request type > Add "Test" CF under Request Form so that it displays in Portal
- Create a new issue from portal and fill up "Test" CF
- Back to Agent view, you notice that "Test" CF isn't shown under "Bear" tab, but it's in "General"/ main tab
Suggested resolution
Show the field in a tab as per screen configuration (regardless if it's added in Request form)
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDCLOUD-9793] Show fields in a tab as per screen configuration
Hoping to get this assigned as well, we have at least a few fields we'd like to move to a separate tab that may not get used as often as others
We also have customers that are interested in this feature. They want to organize how fields are presented in the agent view, but it is not possible currently. Maybe this should be assigned to someone that is active?
Hello,
Could this issue be reviewed? When we have big form on the portal we want the agent to be able to see the ticket by section so all information related to one subject is all together. It causing the agent to missed out on data entered if distracted.
Thank you,
I'm surprised this feature request has been open for over a year. Please fix this asap, there are a lot of us waiting to use this option.
Even though this is something not common: having a JSM project with tabs on the Service Desk Team side, it is totally not expected. It would be great if at least there would be a warning on the request types section, or somewhere around to know in advance that this would happen.
Of course fixing this is the best solution, but in the meantime, maybe there is something easier to do.
Pinning fields is also not possible when these fields are present on the matched request type.
PLEASE assign this to someone in Atlassian who is ACTIVE, thanks!