feat(custom-fields): Add support for CMDB object fields#937
Draft
RoderickJDunn wants to merge 1 commit intoankitpokhrel:mainfrom
Draft
feat(custom-fields): Add support for CMDB object fields#937RoderickJDunn wants to merge 1 commit intoankitpokhrel:mainfrom
RoderickJDunn wants to merge 1 commit intoankitpokhrel:mainfrom
Conversation
CMDB (Assets/Insight) object fields require JSON array format with
workspaceId, id, and objectId properties. Previously, the CLI passed
these values as escaped strings, causing "expected Object" errors.
This change:
- Adds customFieldFormatCMDBObject constant for "cmdb-object-field" type
- Parses JSON input for CMDB fields in constructCustomFields()
- Handles CMDB fields in constructCustomFieldsForEdit() with proper
"set" semantics for edit operations
Usage:
jira issue create --custom cycle='[{"workspaceId":"...","objectId":"24"}]'
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
format
expected Objecterrors from the Jira API
Problem
When creating/editing issues with CMDB object fields:
The CLI would send the value as an escaped string instead of a parsed JSON object:
{"customfield_15259": "[{"workspaceId":"..."}]"} // Wrong - escaped string
{"customfield_15259": [{"workspaceId":"..."}]} // Correct - JSON array
Changes
Test plan