adjusting Jira link for 4.14

[kalexand-rh]

4.14 only

QE not required

Related to https://issues.redhat.com/browse/CCSENABLE-529

Preview: https://67051--docspreview.netlify.app/openshift-enterprise/latest/support/getting-support

If you click the link, it should try to open a Jira in the OCPBUGS project with a 4.14 affects version.

[ocpdocs-previewbot]

🤖 Build preview is available at:
https://67051--docspreview.netlify.app

Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/30753

[bburt-rh]

lgtm

[bergerhoffer]

@kalexand-rh we're seeing a merge conflict due to this change, that it went to 4.14/4.15 and not main. Can this be cherry picked to main too?

[kalexand-rh]

@bergerhoffer, it's version-specific, but there's no reason it couldn't go to main. I also think that it's small enough to risk a bot CP to main. If that goes poorly, I'll open a manual one.

[kalexand-rh]

/cherrypick main

[openshift-cherrypick-robot]

@kalexand-rh: #67051 failed to apply on top of branch "main":

Applying: adjusting Jira link for 4.14
Using index info to reconstruct a base tree...
M	modules/support.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/support.adoc
CONFLICT (content): Merge conflict in modules/support.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 adjusting Jira link for 4.14
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Details

In response to this:

/cherrypick main

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.