| << Back to previous view |
|
[QB-3223] Audit log search broken
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 8.0.10 |
| Fix Version/s: | 8.0.12 |
| Type: | Bug | Priority: | Major |
| Reporter: | AlSt | Assigned To: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| File Attachments: |
audit-log-problem.jpg
|
| Description |
|
How to reproduce
* Open Administration -> Audit log * Click "No Build Requests" ----> works (build requests are filtered out) * Open Administration -> Audit log * Navigate to the bottom and enter something in the input field for textual search * Click on the search button -> instant 200 response but without any change * Consecutive clicks on e.g. the page numbers or on "No Build Requests" are not working anymore. * Audit log UI can only be used after a browser refresh of the whole site. |
| Comments |
| Comment by AlSt [ 19/Jul/18 01:17 PM ] |
|
It seems that the audit logging has more problems.
Build requests are listed although I checked the "No Build Requests" and also the configuration is just prepended to the build request message. This might also be the root cause of the problem we've seen recently that configurations which have "Audit build requests" set to "yes" have no audit logs in their configuration audit logs. |
| Comment by Robin Shen [ 19/Jul/18 11:59 PM ] |
|
The first issue looks like an UI issue.
The second issue is caused by migration. Can you please run some new builds to see if configuration name is still being appended to the message? |
| Comment by AlSt [ 23/Jul/18 05:21 AM ] |
|
Basically these are new audit entries. We did the upgrade to 8.0.10 already some weeks ago.
I checked again and the last wrong audit log message with configuration path in the message was from 5 minutes ago. |
| Comment by AlSt [ 02/Mar/20 12:06 PM ] |
| Actually with 8.0.28 the build request audit log entries not being added to a configuration is still an issue. We sadly did not yet update to 9.x. Do we know if this is fixed there? |