Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error while creating issue with custom field #753

Open
josete89 opened this issue Jul 31, 2024 · 1 comment
Open

Error while creating issue with custom field #753

josete89 opened this issue Jul 31, 2024 · 1 comment

Comments

@josete89
Copy link

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

  1. JiraCLI Version:
    (Version="1.5.1", GitCommit="0e0f82d52ef5a775d2cc662fbe38d9732b9b5c59", CommitDate="2024-01-20T10:48:06+00:00", GoVersion="go1.21.5", Compiler="gc", Platform="darwin/amd64")
  2. Are you using Jira cloud or on-premise jira server?
    Version:         9.12.3
    Build Number:    9120003
    Deployment Type: Server
    Default Locale:
    
  3. What operating system are you using? Also mention version.
    macOS Sonoma 14.4.1
    
  4. What terminal are you using? Also mention version.
     iTerm 2 Build 3.5.3
    

To Reproduce

Steps to reproduce the behavior:

  1. 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:
Screenshot 2024-07-31 at 12 54 26

Then I've tried in to edit the issue and add the value in the we and I saw the following payload:

{"name":"Create+a+confluence+page+with+the+final+architecture.","checked":false,"mandatory":true,"globalItemId":0,"statusId":"none","rank":0,"id":1,"dueDate":null,"isHeader":false,"priorityId":null,"assigneeIds":[],"version":"5.0","linkedIssueKey":null}

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

@ankitpokhrel
Copy link
Owner

I think we don't support the item type of checklist-item (can't find it in the docs).

We'd first need to figure out how the Jira is expecting the data to be passed for this type. Wondering if you'd be able to help with that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants