Description of problem:
Links to Issue Tracker issues (e.g. as in <https://partner-bugzilla.redhat.com/show_bug.cgi?id=584384#c12>) still refer to deprecated https://enterprise.redhat.com/issue-tracker/* URLs rather than current
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Access a bug that has links to Issue Tracker issues in it. Examine URL.
URL has "enterprise.redhat.com" hostname component.
URL has "access.redhat.com" hostname component.
Lisa, I would also like your approval of this change before I have eng-systems do it.
Are access.webqa.r.c. and access.redhat.com configured to talk to Bugzilla qa and prod env on the network level?
(In reply to comment #2)
> Are access.webqa.r.c. and access.redhat.com configured to talk to Bugzilla qa
> and prod env on the network level?
Never mind, I think access.r.c. is talking to bugzilla today. Let me check with Prod Control.
I got the apache access logs from access.redhat.com/issue-tracker instance. According to the access log, bugzilla.redhat.com is talking to access.r.c. today. Basically the requests to enterprise.redhat.com/issue-tracker/xmlrpc.server.php are all redirected to access.redhat.com/issue-tracker/xmlrpc.server.php
You can go ahead with the url change.
Ok. I have put in request to have this changed on production servers. Closing.