#2794 Trac URL redirection
Closed: fixed Opened by edewata.

There are currently many Bugzilla tickets, documents, or code referring to upstream PKI tickets using Trac URLs which no longer work. If followed, the URLs will now redirect to a generic landing page: https://fedoraproject.org/wiki/Infrastructure/Fedorahosted-retirement

Those URLs probably can/will never be updated. So, to prevent confusions they should be redirected automatically to the corresponding Pagure tickets.

The Trac ticket URL is in this format:
https://fedorahosted.org/pki/ticket/{ID}

The corresponding Pagure ticket URL is in this format:
https://pagure.io/dogtagpki/issue/{ID}


Metadata Update from @mharmsen:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None
- Issue set to the milestone: 0.0 NEEDS_TRIAGE

Filed https://pagure.io/fedora-infrastructure/issue/6375.

Metadata Update from @mharmsen:
- Issue set to the milestone: 1.0 TASKS (was: 0.0 NEEDS_TRIAGE)

Metadata Update from @mharmsen:
- Issue assigned to mharmsen

Metadata Update from @mharmsen:
- Custom field cc adjusted to vakwetu,edewata,cfu,jmagne,ftweedal,nkinder

Filed https://pagure.io/fedora-infrastructure/issue/6375.

Closing this bug since it should have been addressed by the above.

Please re-open this issue if any problems are still encountered.

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

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