Skip navigation

To make output more readable service request inputs should have 'displayed' and 'stored' value to map to incident

score 10
You have not voted. Not Planned

A common scenario with my organization is that we have upwards of 15 questions on a service request in which most of the questions will be sent to the detail field of the resulting incident.  We choose to include the prefix when mapping so it is clear what the resulting values sent there correspond to.  However, it is very common for a question to be rather long and causing a hard to read long test field e.g. "For recurring member listener audit report requests, how often do you want to receive the final report?" it would be ideal if the actual prefix used for this question was "Report Frequency:" so the displayed value on the service request would be the former and shortened version the stored value for the prefix that gets mapped to the incident or task.  Are questions could often be shorter if help text was fixed or more obvious that a hover over on the service request but as it stands users rarely see the hover tips.

 

So then when these inputs are merged into the description field of an incident it would look like this

 

Report Frequency: Monthly

 

Instead of

 

For recurring member listener audit report requests, how often do you want to receive the final report?: Monthly

 

A workaround for me is using the hover over tooltip for the full question but our users aren't noticing having a hover over tool tip.

Comments

Vote history