This is a bit long-winded, so bear with me (sorry!).
I have been working on an application for a customer which creates support tickets from a web form. Due to the (legacy) backend system being used, most of the form data is compiled in the backend and compiled into a single “field” named “description”. All support tickets are displayed in a table from the database with various columns (as per this screenshot below) but the aforemenetioned “description” field is not displayed in the table summary as the content of this compiled field could be very lengthy and therefore, it was determined to exclude from the table (it is visible on each single ticket view (click-through from table)).
The requirements have just changed due to a customer requested feature, namely to be able to search/filter on the originally completed form and this hidden, compiled “description” field directly from the database view above.
Now, devs have informed me that it is totally possible to do this but my (UX/UI) challenge is how to display this in the current table in an elegant manner. My first thoughts are to change the “Subject” column, which already has a free-form search field, to “Subject/Description” (still not going to display this content in table though) and when users search/filter using this field, it will also return (filter) results from the description field but how can I possibly display this/articulate it to those using the form?
Any ideas much appreciated and if this makes no sense (likely), feel free to ask me to expand on this…