Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add createdAt to sortField options in queryStatuses #2361

Open
shawnphoffman opened this issue Mar 21, 2024 · 2 comments
Open

Add createdAt to sortField options in queryStatuses #2361

shawnphoffman opened this issue Mar 21, 2024 · 2 comments

Comments

@shawnphoffman
Copy link

Is your feature request related to a problem? Please describe.

This is a feature request to support a change I would like to make in the Ozone UI. I would like to add createdAt to the UI and make it sortable to make it easier to view content labeled via automation (e.g. no report).

Describe the solution you'd like

I would like createdAt to be an option for sorting in queryStatuses here

Describe alternatives you've considered

I have not tried anything else

Additional context

This is the UI change I would like to make.
image

@bnewbold
Copy link
Collaborator

Have you tried the "Events" view (link the left-hand column)? That is intended to be a more general purpose query interface, while the "Queue" view is sort of intentionally limited in power/complexity to specific work queues. The design is different (list of events vs a table view), but that could be changed.

@shawnphoffman
Copy link
Author

I've seen the "events" feed but the UI isn't as intuitive as the table layout for me. I think my issue is two-fold. I have an automation that is labeling posts as they come through the firehose and I'm only firing emitEvent > modEventLabel so reviewed/reported is blank and the resulting records just kinda float there since none of the filters target records like that.

I thought about changing the automation to immediately fire emitEvent > modEventAcknowledge to help get them in a different state but I didn't want to do that if it's an anti-pattern.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants