The resource filter dropdown in the HTTP request log was using the order returned by the audit-log filter attributes API. That API collected distinct resource IDs from log rows, fetched resource names, and returned the merged result without sorting. As a result, the dropdown order could appear ID-based, log-order-based, or otherwise inconsistent with the public resources view.
This change sorts resource filter options by resource name before returning them from the audit log APIs. It also applies the same ordering to access and connection log resource filters so similar dropdowns stay consistent.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/fosrl/pangolin/pull/3119
**Author:** [@Adityakk9031](https://github.com/Adityakk9031)
**Created:** 5/20/2026
**Status:** ✅ Merged
**Merged:** 5/28/2026
**Merged by:** [@oschwartz10612](https://github.com/oschwartz10612)
**Base:** `main` ← **Head:** `#3086`
---
### 📝 Commits (1)
- [`73e9e83`](https://github.com/fosrl/pangolin/commit/73e9e830c39d92e16a222e6e8570cc587c6bfc9e) Sort resource filter options in audit logs
### 📊 Changes
**3 files changed** (+45 additions, -3 deletions)
<details>
<summary>View changed files</summary>
📝 `server/private/routers/auditLogs/queryAccessAuditLog.ts` (+15 -1)
📝 `server/private/routers/auditLogs/queryConnectionAuditLog.ts` (+15 -1)
📝 `server/routers/auditLogs/queryRequestAuditLog.ts` (+15 -1)
</details>
### 📄 Description
## Description
Fixes #3086.
The resource filter dropdown in the HTTP request log was using the order returned by the audit-log filter attributes API. That API collected distinct resource IDs from log rows, fetched resource names, and returned the merged result without sorting. As a result, the dropdown order could appear ID-based, log-order-based, or otherwise inconsistent with the public resources view.
This change sorts resource filter options by resource name before returning them from the audit log APIs. It also applies the same ordering to access and connection log resource filters so similar dropdowns stay consistent.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/fosrl/pangolin/pull/3119
Author: @Adityakk9031
Created: 5/20/2026
Status: ✅ Merged
Merged: 5/28/2026
Merged by: @oschwartz10612
Base:
main← Head:#3086📝 Commits (1)
73e9e83Sort resource filter options in audit logs📊 Changes
3 files changed (+45 additions, -3 deletions)
View changed files
📝
server/private/routers/auditLogs/queryAccessAuditLog.ts(+15 -1)📝
server/private/routers/auditLogs/queryConnectionAuditLog.ts(+15 -1)📝
server/routers/auditLogs/queryRequestAuditLog.ts(+15 -1)📄 Description
Description
Fixes #3086.
The resource filter dropdown in the HTTP request log was using the order returned by the audit-log filter attributes API. That API collected distinct resource IDs from log rows, fetched resource names, and returned the merged result without sorting. As a result, the dropdown order could appear ID-based, log-order-based, or otherwise inconsistent with the public resources view.
This change sorts resource filter options by resource name before returning them from the audit log APIs. It also applies the same ordering to access and connection log resource filters so similar dropdowns stay consistent.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.