-
Bug
-
Resolution: Done-Errata
-
Normal
-
4.13
-
None
-
Moderate
-
No
-
1
-
Sprint 239
-
1
-
Rejected
-
False
-
-
N/A
-
Release Note Not Required
Description of problem:
Reported in https://github.com/openshift/cluster-ingress-operator/issues/911
When you open a new issue, it still directs you to Bugzilla, and then doesn't work.
It can be changed here: https://github.com/openshift/cluster-ingress-operator/blob/master/.github/ISSUE_TEMPLATE/config.yml
, but to what?
The correct Jira link is
https://issues.redhat.com/secure/CreateIssueDetails!init.jspa?pid=12332330&issuetype=1&components=12367900&priority=10300&customfield_12316142=26752
But can the public use this mechanism? Yes - https://redhat-internal.slack.com/archives/CB90SDCAK/p1682527645965899
Version-Release number of selected component (if applicable):
n/a
How reproducible:
May be in other repos too.
Steps to Reproduce:
1. Open Issue in the repo - click on New Issue 2. Follow directions and click on link to open Bugzilla 3. Get message that this doesn't work anymore
Actual results:
You get instructions that don't work to open a bug from an Issue.
Expected results:
You get instructions to just open an Issue, or get correct instructions on how to open a bug using Jira.
Additional info:
- clones
-
OCPBUGS-12790 Cluster-ingress-operator repo Issues link directs people to Bugzilla
- Closed
- links to
-
RHEA-2023:5006 rpm