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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Unable to create JIRA issue with Cloud.

HI I am trying a rest request but it is throwing an error.

"fields": {
"key": "ABC"
"summary": "Hi",

"issuetype": {
"name": "Bug"


Authorization is API token basic



error is 


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

1 comment

Pavel Junek Community Leader Aug 03, 2019

Hi @saurabh,

Looks like you don't have the Summary field in the Create Screen set in your Jira project.

Please see this Atlassian Community theard - JIRA REST 5.0 - Create Issue Error


I have done all things by setting some permissions. But My question is why JIRA trial version of cloud do not give permission to play with APIs.

NOw you know i have always getting reporter as anonymous, may be i deleted something in screen types or edit fields. Can you tell me how to fix this? I want reporter name as JIRA user but now it is coming as Anonymous if i create via API but manually it is fine..

It does give you permission to use the APIs - the only difference between a trial and paid licence is that the trial will stop letting people use it when the trial expires.  Everything else works the same, including the REST API.

The problem here is exactly what @Pavel Junek said - you do not have the summary on the create screen.  You need to put it back so that the REST call can populate it. 

Sometimes though, this can be down to authentication - can you do anything as the user you are using for REST?  A simple call to see what comes back if you just read an issue?


Log in or Sign up to comment