Adding Assignee Field to the Table
Asked by Jakob Hernandez:

The data source that was added to connect to doesn't have the Assignee field there without having to do extra configurations on a separate Google Spreadsheet.

What are the steps to get a column for the Assignee field to view who is assigned that issue on the table when added to an Atlassian Analytics dashboard?

(Asking here as it seems each time it's there and the next day it's not - curious how to build that string if it's not already there and was before)


Answers:
author: Jessie Turpin
body: Hi Jakob,

To find the assignee of an issue, you can use the *Assignee account ID* column from the [Issue table](https://support.atlassian.com/analytics/docs/schema-for-jira-family-of-products/#Issue). Note that if your organization is a managed account, the [Account table](https://support.atlassian.com/analytics/docs/schema-for-organization-data/#Account) in the Atlassian Data Lake will have the user's names as well. Then including the *Name* column from the Account table would let you see the assignee's by name instead of by account ID. You can use the "Top 5 assignees by open issue count" chart template to get an idea of how to query the assignees by name in Atlassian Analytics.

Let us know if you have any additional questions.

comments: author: Abc
body: .


author: Furlong_ Andrew
body: Hi Jessie,

I tried to follow the steps you described to get the assignee names for Jira issues, but found that my queries often returned incorrect names - users would be assigned multiple codes incorrectly, and the true assignee names are missed. Do you have any idea what could be causing this error?

Thanks!


author: Jessie Turpin
body: Hi Andrew! Could you check that the join path is using the **Assignee account ID** column to connect the Issue and Account tables? The path highlighted in blue is the current join path used by the query.

![Screenshot 2024-05-16 at 3.23.56?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/324303i133B9814C43C2AD4/image-size/large?v=v2&px=999 "Screenshot 2024-05-16 at 3.23.56?PM.png")

It's possible that your query may be using the Creator or Reporter account ID instead, which could explain the incorrect names. If an incorrect join path is used, just click on the line using the Assignee account ID column to connect the two tables and re-run the query to help the join path update.

If the query is using the Assignee account ID column in the join path, you can [create a support ticket](https://support.atlassian.com/contact/) with our team to help us troubleshoot further.


author: Furlong_ Andrew
body: Hey Jessie! I'm using the correct join path between Assignee account ID and Account ID. When I ran the same query within a chart (as compared to when I was building a custom table earlier) I was able to get the correct results. Do you have any idea why it wouldn't have worked when I tried to save the results to a custom table?


author: Jessie Turpin
body: Hey Andrew! It's hard to say what may be going wrong without getting to look at the code used to create the chart and the SQL you were using for the custom table. Could you create a support ticket with the team so we can investigate this further for you? Thanks!