nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira Team REST API to get issue details

Akash Gunjal_o519vz

I am trying to get the data under specific reporting mechanism, Like There is Manager->Engineering Leaders-> Engineers (Users). I want to get data of issues where assignees reporting hierarchy is aligned to specific users. I want to pull engineering leader wise data for specific leader. Is there any APIS exist for this scenario ?

Sam Ray (CXO) -> 15 Engineering leaders -> Engineers working among leaders

I want to pull issues where issue assignee hierarchy is belongs to one of the engineering leader

Accepted answers

All comments

Arkadiusz Wroblewski

Hello @Akash Gunjal

Is this about Jira Server or Jira Cloud?

Also we need more context what you wanna achieve.

Best,

Arkadiusz 🤠

Trudy P Claspill

Hello @Akash Gunjal

Welcome to the Atlassian community.

Can you clarify if you are using the Jira Cloud (software-as-a-service) product or the self-hosted Server/Data Center product? If you click the Help button in Jira (near your avatar in the upper right corner) and select About Jira, what do you see in the pop up for a version number?

You mention the Team API in you summary. Have you defined Teams in you environment and assigned the engineers and leaders to the Teams? Are you then setting the Team field for each issue?

Do you have user groups defined where you have assigned all the engineers under a specific leader to a group?

Are you using the Assets feature where you have a record for each engineer that includes an attribute that identifies their leader?

Without a set up like one of the above there is nothing native in Jira that will enable you to get all the issues assigned to engineers under a specific leader by specifying the leader in the query. You have to have some feature already in place that establishes the relationship between each engineer and a leader, like a Team, a user group, or Asset objects.

Otherwise all you can do is manually construct a query such as

assignee in (engineer1, engineer2, engineer3)

...manually supplying the list of engineers under a specific leader.

Rik de Valk (Brainboss)

Hi @Akash Gunjal ,

If you have organised all engineers into Teams you can use the JQL

assignee in membersOf("id:<teamId>")

in an API call to search for issues using the /rest/api/3/search/jql endpoint.

Alternatively, if you have organised in Groups, then you can use the same JQL, but by providing the Group

assignee in membersOf("Group")

Hope that helps.

Have a nice day!

Rik

Akash Gunjal_o519vz

Hello @Trudy P Claspill , Thanks for your response. I am using Jira Cloud (SAAS). I am Not tagging any teams or leaders to issues in Jira.

It is like if I hover on assignee profile its redirecting me to Teams page where I can see reporting line.

Now as shown on above Image I want to get all issues where assignees are reporting to Rajnish. Under Rajnish there are 15 leaders are working and below that there are engineers who are working on Individual Jira issues. I want to pull data which can show all data engineering leader wise to Rajnish.

Akash Gunjal_o519vz

Hello @Arkadiusz Wroblewski , Thanks for your response can you please check first comment response I am trying to achieve that

Akash Gunjal_o519vz

Hello @Rik de Valk _Brainboss_ , as of now no I mean I have not created any specific team or related to leaders. Can you help me understanding how we can create group in Atlassian Teams?

Trudy P Claspill

As I said if you are not adding a Team or User Group to each issue, where that Team or Group contains the engineers under a particular Leader, there is not a native JQL function to get what you want.

This document details how to create Teams.

https://support.atlassian.com/platform-experiences/docs/start-an-atlassian-team/

After Teams have been created, you then need to ensure that the Team field is added to the field configurations and screens for the work item types in all the Spaces from which you want to get data.

You will then have to set the value of the Team field in each work item.

Then you can use the JQL described by @Rik de Valk _Brainboss_ to create a query to retrieve the work items for one team at a time, or modify it to retrieve work items for all Teams thus:

Team is not empty

Or you could use:

Team in (comma separated list of Teams)

If you sort the output by the Team field you will be able to review the results and see the issues for each Team/leader.

Note that Jira does not automatically synchronize or set the Team field based on the value in the Assignee field. In fact that is very challenging to do, because a given Assignee can belong to more than one Team. So the value will need to be managed manually, or you would need to devise a custom solution for figuring which Team to select based on the Assignee.

Arkadiusz Wroblewski

@Akash Gunjal

I checked your response, but @Trudy P Claspill is already helping you very thoroughly. Providing similar solutions would likely only be more confusing. You're in good hands

Best,

Arkadiusz 🤠

Rik de Valk (Brainboss)

Hi @Akash Gunjal ,

You can read all information about Teams here: https://support.atlassian.com/platform-experiences/docs/work-with-atlassian-teams-across-your-products/

Atlassian recently introduced the option to sync Team members with Groups. See https://support.atlassian.com/platform-experiences/docs/create-a-managed-team-from-a-connected-group/

Have a nice day, Rik

Ash H_

Hi @Akash Gunjal

I'm from Appfire's Expert Services, and your question caught my eye.

If you find that you're frequently pulling this data to build custom views or reports that aren't easily available in the standard Jira interface, JXL for Jira can be a real game-changer. It combines the power of Jira with the familiarity of a spreadsheet, allowing you to view and manage your issue details in a highly customizable table format. Based on the public documentation, JXL supports advanced features like nested issue grouping and custom hierarchies, which means you can organize your issues by assignee or other criteria and see them rolled up into organizational structures. This can often replace the need for custom API scripts when your goal is simply to get a clearer, more structured view of your project data for reporting or bulk editing.

For teams that need to take this data a step further into long-term planning and capacity management, BigPicture is a fantastic complementary tool. It provides a dedicated Resources module and robust reporting capabilities designed to help you monitor team capacity and aggregate data across multiple projects. While JXL is excellent for fast, spreadsheet-style interaction with your issue details, BigPicture excels at visualizing how those issues fit into a larger roadmap or portfolio, ensuring that your team's workload remains balanced and aligned with your broader strategic goals.

Best of luck,
Ash

Kh_Safal

Hi @Ash H_, we noticed you posted promotional content in multiple places across the forums, which is against our Atlassian Partners - Rules of Engagement. I’ve removed the duplicate/promotional posts and kept this one live.

Please also take a moment to review our rules so you're aware for next time. Also, if you're part of a Marketplace App team, we’d like to ask you to follow the steps outlined here to get an “Atlassian Partner” lozenge for your profile.

Thanks!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

jiracloud