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

do you have any idea on how to capture the JIRA Issue IDs that gets linked in a bamboo build number?

do you have any idea on how to capture the JIRA Issue IDs that gets linked in a bamboo build number?

2 answers

1 vote
robhit Atlassian Team Nov 10, 2017

I am not quite sure what is the requirement here, could you please rephrase your question with an example?

For each build jira issues has been attached and it will be display in issues tab on the bamboo builds we want to capture those jira I'd and tasks in text or csv file is this possible

robhit Atlassian Team Nov 13, 2017

refer bamboo REST API doc -



Thanks Rob hit I am able to see the jira as issue key and jira summary is there any way to download those two values alone if that is done we are good could you please help us

robhit Atlassian Team Nov 21, 2017

How about using below REST API:

curl -X GET --user username:password -H 'X-Atlassian-Token: no-check' "http://localhost:8085/rest/api/latest/result/PF-AT-16?expand=jiraIssues"

Where "PF-AT-16" is the plan key and build number.

The above will give you the Jira issues linked to the build number.

Mind that HTTP basic authentication with username and password has been deprecated. You should use a personal access token as a Bearer credential in an HTTP Authorisation header.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events