#2686 Upgrade script for audit event names
Closed: fixed by mharmsen. Opened by edewata.

Some audit event names are changed as part of audit event improvements (ticket #2635). There should be an upgrade script to change the audit event names in CS.cfg in the existing instances.


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 type adjusted to defect
- Custom field version adjusted to ''
- Issue priority set to: critical
- Issue set to the milestone: 10.4

Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1404075, https://bugzilla.redhat.com/show_bug.cgi?id=1445532

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5 (was: 10.4)

Metadata Update from @mharmsen:
- Issue priority set to: major (was: critical)

Per CS/DS Meeting 09/25/2017: 10.5 blocker

Metadata Update from @mharmsen:
- Issue priority set to: blocker (was: major)

Metadata Update from @edewata:
- Issue assigned to edewata

Metadata Update from @mharmsen:
- Issue priority set to: critical (was: blocker)

Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1539897 https://bugzilla.redhat.com/show_bug.cgi?id=1539906 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1404075, https://bugzilla.redhat.com/show_bug.cgi?id=1445532)
- Issue priority set to: blocker (was: critical)
- Issue set to the milestone: 10.6 (was: 10.5)

Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1539897,https://bugzilla.redhat.com/show_bug.cgi?id=1539906 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1539897 https://bugzilla.redhat.com/show_bug.cgi?id=1539906)

Metadata Update from @edewata:
- Issue priority set to: critical (was: blocker)

Per 10.5.x/10.6 Triage: 10.5

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5 (was: 10.6)

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.6 (was: 10.5)

Metadata Update from @edewata:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1539897 https://bugzilla.redhat.com/show_bug.cgi?id=1539906 https://bugzilla.redhat.com/show_bug.cgi?id=1666921 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1539897,https://bugzilla.redhat.com/show_bug.cgi?id=1539906)

Metadata Update from @edewata:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1539897,https://bugzilla.redhat.com/show_bug.cgi?id=1539906,https://bugzilla.redhat.com/show_bug.cgi?id=1666921 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1539897 https://bugzilla.redhat.com/show_bug.cgi?id=1539906 https://bugzilla.redhat.com/show_bug.cgi?id=1666921)

Metadata Update from @mharmsen:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

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/2806

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata