Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

How to read summary of Jira story via API

Hi Jira experts,

I wonder if anyone can help me with the following... 

We have created an integration between our INM ideation platform and Jira.

INM Campaign is mapped with Jira project

INM idea is mapped with Jira story


Basically when we create an Idea on INM, the integration will create a respective story on Jira side.

Then on INM side, we wish to display the info from the Jira story

here we have a problem: we cannot find a way to display the summary of the Jira story


We are following this documentation:

under "Input data":

{ "fields": { "project": { "key": "TEST" }, "summary": "REST ye merry gentlemen.", "description": "Creating of an issue using project keys and issue type names using the REST API", "issuetype": { "name": "Bug" } } }


Thus there are 2 fields only from server while creating object (Jira story) - id and key. The id is an internal number and key is the story key

How can we have an additional option for object summary?


Thanks in advance for any help on this.


David CK



1 answer

Hi @david cockrell , welcome on the community. I the steps should be as follows:

  1. you call Jira REST Endpoint to create a story. It must contain some mandatory fields like project->key, issuetype->name, summary, description
  2. the pair of key and id is returned as a response
  3. you need to store id or key in INM solution
  4. you call /rest/api/2/issue/{issue id or key} to get the summary -> you always get story in current status, so if anyone changes the summary, new summary is loaded in INM

Did I understand your problem correctly?

Hi Martin,


Thanks for your reply. (and sorry for the delay in my response)

We use this method while we perform update procedure.

But what we need is to get summary filed in the response of the create procedure.

I.e. When I post to /rest/api /2/issue to create a ticket, I want a summary field in response.


Any suggestions on this would be dearly appreciated :-)


Kind regards,

David CK

Hi @david cockrell I still don't get the use case.

Summary is something you send with your request from client's side. So you have this information on client side already.

The description of POST method is here:

Only ID and Key attributes are returned during the creation.

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