There should be audit logs generated for the following events:
Metadata Update from @edewata: - Custom field component adjusted to General - Custom field feature adjusted to '' - Custom field origin adjusted to Community - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1404080 - Custom field type adjusted to defect - Custom field version adjusted to ''
Metadata Update from @edewata: - Issue priority set to: 1 - Issue set to the milestone: 10.4
Metadata Update from @edewata: - Issue assigned to edewata
Metadata Update from @edewata: - Issue priority set to: 2 (was: 1)
Metadata Update from @edewata: - Custom field blockedby adjusted to https://pagure.io/tomcatjss/issue/4
https://review.gerrithub.io/#/c/354391/
Metadata Update from @edewata: - Issue close_status updated to: fixed - Issue set to the milestone: 10.4.1 (was: 10.4) - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Custom field fixedinversion adjusted to pki-core-10.4.1-1.fc27
Additional changes in master: * 4ab0608cbda0c9336c5eb9ea40a7d3ca769ab17b
Fixed missing ClientIP field: * c381566ddf1f4f05330063bb012d59e5c1753b13
Metadata Update from @mharmsen: - Issue set to the milestone: 10.4.2 (was: 10.4.1)
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/2722
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.