Who would benefit? |
Users and administrators |
What impact would it make? |
Having different formats is visually confusing - especially for US/EU users or solutions with multiple tenants and formatting-rules for date/time-values |
How should it work? |
The List-view in the query-table should always use the same format. |
Why is it needed? |
Because it cannot possible be "working as intended", and customers trust in the quality of the solution plummets with these easily-avoidable mistakes. |
Additional feedback, background or context:
When performing a query, you sometimes (often even) want to do "something" based on the "Created date" and "Modified date". However, when inspecting the List-view of the query-result-page, date-formats vary.
In the attached screenshot, the first line highlights the issues. The same product - the same line - has two different formats;
the time-format is US in the "created"-column, but EU in the "modified"-column
there's a comma separating the date from the time in the "created"-column, but not in the "modified"-column
Overall, this seems sloppy, and as a partner, we are at risk of our users losing trust in the quality of the overall solution.