You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are you using Jira cloud or on-premise jira server?
Version: 9.12.3
Build Number: 9120003
Deployment Type: Server
Default Locale:
What operating system are you using? Also mention version.
macOS Sonoma 14.4.1
What terminal are you using? Also mention version.
iTerm 2 Build 3.5.3
To Reproduce
Steps to reproduce the behavior:
jira issue create -PDPE-719 -lplatform-evolution -s"Define Technical Specification for XX" -b"In order to proceeded with the implementation is need to define the low level architecture to implement the whole service." --custom=acceptance-criteria="Create a confluence page with the architecture" -tStory --debug
Expected behavior
Create the issue with the custom field:
Screenshots
I've checked the jira config file to verify the custom field:
Then I've tried in to edit the issue and add the value in the we and I saw the following payload:
In contrast what the cli is sending is the following:
{"update":{},"fields":{"customfield_10012":"DPE-719","customfield_10200":["Create a confluence page with the architecture",""],"description":"In order to proceeded with the implementation is need to define the low level architecture to implement the whole service.","issuetype":{"name":"Story"},"labels":["platform-evolution"],"project":{"key":"DPE"},"summary":"Define Technical Specification for XXX"}}
Additional context
The text was updated successfully, but these errors were encountered:
Describe the bug
I'm trying to create a issue with a custom field and I got a 500 error from jira.
Please provide following details
(Version="1.5.1", GitCommit="0e0f82d52ef5a775d2cc662fbe38d9732b9b5c59", CommitDate="2024-01-20T10:48:06+00:00", GoVersion="go1.21.5", Compiler="gc", Platform="darwin/amd64")
To Reproduce
Steps to reproduce the behavior:
jira issue create -PDPE-719 -lplatform-evolution -s"Define Technical Specification for XX" -b"In order to proceeded with the implementation is need to define the low level architecture to implement the whole service." --custom=acceptance-criteria="Create a confluence page with the architecture" -tStory --debug
Expected behavior
Create the issue with the custom field:
Screenshots
I've checked the jira config file to verify the custom field:
Then I've tried in to edit the issue and add the value in the we and I saw the following payload:
In contrast what the cli is sending is the following:
Additional context
The text was updated successfully, but these errors were encountered: