Allow Alert API endpoint to be sorted by newest issue first #1031
Assignees
Labels
bug
Something isn't working
Comments
|
Sounds like a bug for me, worth fixing. |
|
Taking this one to the core team's backlog. |
|
@jtheory I think it's purely backend |
github-merge-queue bot
pushed a commit
that referenced
this issue
Jun 29, 2023
# What this PR does Change alerts order in `/alert` public api endpoint ## Which issue(s) this PR fixes #1031 ## Checklist - [x] Unit, integration, and e2e (if applicable) tests updated - [x] Documentation added (or `pr:no public docs` PR label added if not required) - [x] `CHANGELOG.md` updated (or `pr:no changelog` PR label added if not required)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current functionality of the Alerts API endpoint is to return alerts by
created_atin ascending order. This means our oldest alerts will always be at the top of the response. For our use cases, this is pretty inconvenient. It would be nice if this endpoint returned the newest alerts first with the older alerts following thereafter. This doesn't necessarily need to be default behavior, and could be locked behind a query parameter.The text was updated successfully, but these errors were encountered: