[RFE] Enhance service -> requests and automation -> requests to add better filtering options

[jrafanie]

Any of these items can be extracted to a new issue or implemented separately.

Evaluate if they make sense, make adjustments and let's discuss.

• Add filtering by state/status (ok/error/failed).
  • Ensure we add the last message and a link to the request so the user can navigate from errors to the new task/request logging added by @DavidResende0
• Add filtering by custom time interval
  • I'm not sure why we are limited to a dropdown of options instead of 2 date pickers for start and end time. Perhaps to avoid getting burned by too much data, but we should be able to implement a limit/offset for paging if we do it in the API. Maybe limiting it to a week range at most would make sense.
• Add filtering by catalog type or by name. We'd need a database with different types of service requests and instances of the same one to better describe this but the idea is we want to be able to see how successful/unsuccessful a specific type of service request has been. Then, drill down into the reasons why it failed. * Filtering by requester should work. With older versions "all" was the only option. * Ensure the visible truncation with ... should be expanded when there is space available. Needless shrinking of the important report columns should be minimized. Also, the alt text popup when you hover over it should not be truncated with ellipsis.

For example, we can only filter by requester, pending, approved, denied, etc.

Whereas Settings -> Tasks, we can filter by queue states/status including ok/error/warn/running/queued/finished/etc.

[jrafanie]

cc @GilbertCherrie

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.