I'm setting up user portal and Service Desk queues to handle reported issues and requests.
I'm using Extension for Jira Service Desk to get access to Dynamic Forms that allows quick and easy Request / Incident form configuration.
I just found out that Service Request tickets show some details that were not supposed to be shown.
So for example if I use Data Backup Request i created - on the portal it looks good - it present all required fields. But then when i open ticket in Service Desk queue, in details view i can see values for fields from other requests (for example intended for Mailbox access).
Can't find any place that holds this ticket details configuration.
- portal view1 - that shows request form with all required fields
- portal view2 - that shows details presented to end user after creating ticket (details marked yellow are unintended for this request form and was not presented on above Request Creation form)
-sd ticket view1 - showing Service Desk agent view of this ticket - again yellow are uninteded details for this request
- admin "where is my field view" - showing some info about this additional fields.
Marked yellow is information that unintended field has a value for this issue - and i have no idea where this value comes from
I created a list of custom fields that works correctly in different forms. I dont know why these few here are presented between different request forms details view.
Can you please give me a hint where can i look for some configuration that is responsible for showing these details?
Welcome to the Community. You will need to adjust the issue type Screen Scheme associated to your Request Form's issue type (NOTE - this screen scheme is different than your setup for the Request Forms for the portal). You can access the screen scheme via "Project settings"> Screens
Once in the Screens Scheme UI, access the screens associated with the appropriate issue type, then remove the fields as needed. When you view the issues in the project UI (not protal UI), the screen is configured/controlled via the project's screen scheme configuration. In Jira/JSM, there are three basic issue screen setup (CREATE ISSUE, EDIT ISSUE, and VIEW ISSUE).
Hope this helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Infrastructure Applications Team
Thank you for quick response.
I still need a clarification here.
As far as I understand changing Screens Scheme UI settings will change it globally.
So if i remove "shared mailbox information" field from Request (both create and edit) Screen it will not be presented on "Backup recovery" form but also will be removed for "Mailbox access request" form?
Do i understand it correctly?
I can't understand why different custom fields i created and set the same way are not displayed here and these few marked yellow are?
After re-analyzed your original ask, you need to look at the field in question to see if it is setup with default value or not. You will need to access Administration > Issues > Custom fields to find out if there is default value configured. If so, you need to clear out the default value.
I am assuming that your Request Type Form (for the Portal UI) for the different types of request are using the same issue type, thus you cannot have default value setup in those fields. In Jira/JSM, if a field has no value associated with it, then it will not be displayed in the ISSUE VIEW screen.
You can disregard my original suggestion. My original suggestion will work if you have different issue types + different screen schemes (not global).
Sorry that I was not clear in my original suggestion.
Hope this helps.
Hello Community! Quick disclaimer: We are running a contest on Community (The Atlympics!) from July 23rd - August 8th of 2021. If you are interested in participating in this contest (prizes! ...
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