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

Unabe to create issue via rest api jira

Unable to run Create Issue rest api call when there are custom screen setup for a project

we have the project XXXXX setup with custom screens and summary field is present under a specific tab. Eg. General Info.  Is that even a possible root cause for this issue or something else? also clone issue option is disabled for this project. Pls advise.


For this scenario, when i try to run create issue api call, i am getting the below response. 



    "fields": {
        "summary":  "test summary",
        "project": {
            "key": "XXXXX"
        "issuetype": {
            "name": "Bug"
    "errorMessages": [],
    "errors": {
        "summary": "Field 'summary' cannot be set. It is not on the appropriate screen, or unknown."

1 comment

@Dhanraj Prabhakaran 

Add the "Summary" field to Jira's main tab.

If you don't reference the read tab, I believe the request won't be able to read.

My recommendation would be to keep all the fields that will be sent in the creation payload, leave them in the standard Jira tab.

Is it possible to reference the "General Info" tab with summary field in request json data?

I don't know exactly if this is possible, what you can do is the following:

Create an issue by filling in the field in several tabs and then GET this issue.

Evaluate the payload behavior to analyze if there is a difference in fields per tab


Log in or Sign up to comment