Created attachment 1518033 [details]
screen capture of issue
Description of problem:
When a service is requested that has drop down items which has Values and Description, the Description is the one that is meaningful to the end user and the value is normally used for the automation.
the user selects the items required and submits the request, when the request is opened by the admin for approval, he can only see the item values which makes no sense to him to decide on the approval.
Version-Release number of selected component (if applicable):
All the time
Steps to Reproduce:
1. create a service dialog with drop down items which has different Value than the description
2. submit a service request using the dialog
3. open the service request for approval or status check and you will find the details of the request containing the item values and not the description that the user has selected.
the item values are displayed
the item description should be displayed
a screen capture video is attached for the issue
This is working as designed. The dialog description helps the user to select the appropriate value(s). Only the dialog values are stored in the request.
Can you look into this to see how difficult it would be to use the dialog description instead of the value?
This one's trivial, I have a fix, I just need to do a bit of testing around multivalue and default value before I open the PR that'll do this.
Fine okay that only works for static fields, as Erik says, we don't store the dynamic values in the same way, please disregard comments 11 and 12.