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

Extracting scrum team members

Is there a way to extract the names of team members and which scrum board they are assigned to? These names are visible at the top of the board as filters, but I am wondering if there is a way to collect these names for all boards. Thanks!

1 answer

1 accepted

1 vote
Answer accepted

Hi @Alice Ou

First, do you have Jira Server or Jira Cloud?

Reason being, there is a messy way to get the data in Jira Server (by accessing the db and writing a query to join agile board with the associated quick filters tables) to see the names of the quick filters. This is really not advisable unless you're comfortable with db and ensure you're using a read-only account to not make any erroneous table updates. Even then, never a good idea to run queries against production. We have a mirrored db for reporting purposes, so I am able to run a few backend queries to see data I couldn't normally see in the UI.

Otherwise, there is not. Quick filters are an attribute of the agile board. Users are an independent object not associated to boards. Users are associated to projects by being (1) an issue assignee, and (2) as a user in a Project Role to a project or part of a "group" assigned to a Project Role. Users are able to see and interact with projects based on project permissions. They're not an entity linked to a board.

I hope that helps.

One additional note, what we do at our company is standardize the naming convention of our agile boards into the "teams" or "squads" that are performing the work.

We keep a separate wiki page of all the "teams", the verticals they support and members of said team. We also used a custom field to track what "team" is related to a Jira issue.

However, you still need to have a table (for us its a page in Confuence) of the mapping. Jira does not natively store a "team" entity. You either create a matching team name in the Local Groups and assign users. Or, you may leverage a wiki page or other stored doc. Keep in mind, depending on how fluid teams are spun up and decommed, you could be looking at a lot of administrative maintenance updating the sources you track for "team".

The closest you may have is "Component" unless you're using "Component" as the product or service delivered in a project. Even then, would still need a source to record "team" or "squad" and the members therein.

Thanks for the comprehensive answer, Ryan. I'll bring these considerations to my technical teammates to see if we can do the db extract/join and how we can build a better infrastructure for tracking scrum team members. Thank you!

Like # people like this

This is a fundamental problem for Jira Agile.  Software Product development is a team sport, what the heck Atlassian's stock symbol on NASDAQ is:TEAM.  Yet they haven't figured out to make "Team" object as a first class citizen in the system in order to harness team level adoption of their tools - unless they see the tools are for bookkeeping and the role of project managers.

They have figured out other objects to represent such as "Org, Project, User". So why not "Team".

May be the stock symbol for Atlassian should be "anything but TEAM".

I hope you see that asking customers to do anything else is a work around, and asking them to taken on Technical Debt as shown above in the work around.

Like # people like this

Suggest an answer

Log in or Sign up to answer