Updating CustomFields for Jira Cloud#741
Updating CustomFields for Jira Cloud#741openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
Conversation
rh-pre-commit.version: 2.3.2 rh-pre-commit.check-secrets: ENABLED
|
/hold |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughTwo Jira custom field constants in the release controller were updated with new field IDs. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Comment |
| JiraCustomFieldFeatureLink = "customfield_12318341" | ||
| JiraCustomFieldReleaseNotes = "customfield_12310211" |
There was a problem hiding this comment.
@hoxhaeris These 2 fields do not seem to exist anymore in either the DC version or Jira Cloud. Not sure how to proceed...
|
@bradmwilliams: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/unhold |
|
/lgtm |
|
[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 DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
rh-pre-commit.version: 2.3.2
rh-pre-commit.check-secrets: ENABLED