How to create JIRA with REST API and "Environment(s) Affected" field

Doug May 15, 2017

We're trying to use the JIRA REST API to create issues on a project.  Below is the command and JSON we're using.  Keep getting a 400 error saying: 

{"errorMessages":[],"errors":{"Environment(s) Affected":"Field 'Environment(s) Affected' cannot be set. It is not on the appropriate screen, or unknown."}}

Any suggestions how we can get the command to run successfully?  The Environment(s) Affected field is a multi-selection field.

 

curl -i -D- -u 'user:pass' -X POST -d @./create_issue.json -H "Content-Type: application/json" https://jira.example.com/rest/api/2/issue/

 

$ cat create_issue.json
{
        "fields": {
                "project":
                {
                        "key": "TEST"
                },
                "summary": "TEST Issue Creation",
                "description": "Testing JIRA integration. Ticket can be closed.",
                "Environment(s) Affected": "None",
                "issuetype": {
                        "name": "Incident"
                }
        }
}

 

screenshot.jpg

 

 

1 answer

1 accepted

0 votes
Answer accepted
josh
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 15, 2017

Hi Doug,

Since "Environment(s) Affected" is a custom field, you will need to refer to it using the "customfield_1234569" notation rather than the field name. Only system fields can be referred to by name. To find the ID for your custom field, you can either pull the createmeta or look in your custom field management page and see the ID in the URL when you're modifying that particular field.

Look for the heading "Example of creating an issue using custom fields" on this page. https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis/jira-rest-api-tutorials/jira-rest-api-example-create-issue

Doug May 17, 2017

Thanks, Josh.  I just tried using the custom field ID and it did work before your answer came in.  Wasn't aware custom fields had to be referenced by the ID.  Wish the error messaging returned would be improved to mention that. 

Suggest an answer

Log in or Sign up to answer