Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Unable to create Issue via REST API


I've seen multiple threads and did go through JIRA REST tutorial.

1. Generated the Access token to use it for Basic Auth. 

Here is the Complete Request:

POST /rest/api/2/issue/ HTTP/1.1
Content-Type: application/json
Authorization: Basic **************
User-Agent: PostmanRuntime/7.13.0
Accept: */*
Cache-Control: no-cache
Postman-Token: 7f778032-b7f7-4d27-80f8-89b522fd72cd,1b0490eb-28d5-4066-8f49-76000b1cebbf
Host: {hostname}
cookie: atlassian.xsrf.token=B2M1-T7HW-8IGG-KJSU_09cc563dfe0ce7f0af5eb9c19b8df3fa4ec60a35_lout
accept-encoding: gzip, deflate
content-length: 278
Connection: keep-alive
cache-control: no-cache

"fields": {
"project": {
"key": "LP"
"issuetype": {
"name": "Story"
"summary": "REST ye merry gentlemen.",
"description": "Creating of an issue using project keys and issue type names u"


Error response


"errorMessages": [],
"errors": {
"summary": "Field 'summary' cannot be set. It is not on the appropriate screen, or unknown.",
"description": "Field 'description' cannot be set. It is not on the appropriate screen, or unknown."

1 answer

1 vote
Andy Heinzer Atlassian Team Jun 14, 2019

Hi Naveen,

I see that you are running into errors when trying to create an issue using the Jira REST API.   That specific error can be very vague. There are a couple of different possible causes for this.

  1. The screens for this issue type do not contain those fields
  2. Your account does not actually have permissions to create new issues
  3. Your REST call is not properly authenticating your credentials, which can lead you to cause #2 again

Could you please let me know what specific tutorial you are attempting to follow?  It could be we have some out dated documentation and I'd like to update that if that is the case here. 

I see you mentioned creating an API Token.  However depending on how you make this request will determine how to use that token. Check out Basic auth for REST APIs for the two different examples. If you were using curl you could use the -u parameters to pass a emailaddress:API_TOKEN as a string to authenticate.  But I suspect that you're not doing that, but rather following the second example where you can supply the auth in a header.  When you do that, you have to encode your username:API_TOKEN into a base64 string first and use that.  You can't just use the API Token directly there.

This could explain the error message you have seen here.

Try that first.  It might also help to start by first making a GET call via the REST API to see if you can return issue data, say GET /rest/api/2/issue/{issueIdOrKey}.  As long as the issuekey you try to retrieve is not publicly accessible anonymously, you will still have to authenticate successfully with an account that can view that issue to get back any data.   It can be a good test to make sure you are authenticated correctly here first.  If that works, then try to make a POST call to see if you can create/save some data.

I hope this helps, please let me know.



Thanks you! this was very helpful

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you