History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-3223
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: AlSt
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
QuickBuild

Audit log search broken

Created: 19/Jul/18 12:12 PM   Updated: 27/Jul/18 03:06 AM
Component/s: None
Affects Version/s: 8.0.10
Fix Version/s: 8.0.12

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
File Attachments: None
Image Attachments:

1. audit-log-problem.jpg
(174 kb)


 Description  « Hide
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.

 All   Comments   Work Log   Change History      Sort Order:
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.

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?

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.