Skip to content

Updating CustomFields for Jira Cloud#741

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
bradmwilliams:custom-fields-update-redux
Mar 16, 2026
Merged

Updating CustomFields for Jira Cloud#741
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
bradmwilliams:custom-fields-update-redux

Conversation

@bradmwilliams
Copy link
Copy Markdown
Collaborator

rh-pre-commit.version: 2.3.2
rh-pre-commit.check-secrets: ENABLED

rh-pre-commit.version: 2.3.2
rh-pre-commit.check-secrets: ENABLED
@bradmwilliams
Copy link
Copy Markdown
Collaborator Author

/hold

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Mar 16, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: d6041603-4c3a-4821-85f3-c82dc433fe88

📥 Commits

Reviewing files that changed from the base of the PR and between a135b83 and c648074.

📒 Files selected for processing (1)
  • pkg/release-controller/release_info.go

Walkthrough

Two Jira custom field constants in the release controller were updated with new field IDs. JiraCustomFieldEpicLink now references customfield_10014 instead of customfield_12311140, and JiraCustomFieldFeatureLinkOnEpic now references customfield_10018 instead of customfield_12313140. These constants are used to locate parent/linked issues in Jira issue data.

Changes

Cohort / File(s) Summary
Jira Custom Field Constants
pkg/release-controller/release_info.go
Updated two public constant values mapping Jira custom field IDs: JiraCustomFieldEpicLink (customfield_12311140 → customfield_10014) and JiraCustomFieldFeatureLinkOnEpic (customfield_12313140 → customfield_10018).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
📝 Coding Plan
  • Generate coding plan for human review comments

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 16, 2026
@openshift-ci openshift-ci Bot requested review from AlexNPavel and hoxhaeris March 16, 2026 09:52
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 16, 2026
Comment on lines 39 to 40
JiraCustomFieldFeatureLink = "customfield_12318341"
JiraCustomFieldReleaseNotes = "customfield_12310211"
Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hoxhaeris These 2 fields do not seem to exist anymore in either the DC version or Jira Cloud. Not sure how to proceed...

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 16, 2026

@bradmwilliams: all tests passed!

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.

@bradmwilliams
Copy link
Copy Markdown
Collaborator Author

/unhold

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 16, 2026
@hoxhaeris
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Mar 16, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 16, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bradmwilliams, hoxhaeris

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [bradmwilliams,hoxhaeris]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot Bot merged commit 7282818 into openshift:main Mar 16, 2026
9 checks passed
@bradmwilliams bradmwilliams deleted the custom-fields-update-redux branch March 16, 2026 10:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants