First, thank you for this integration! It seems very helpful to help managing my team.
I’m currently missing some data because the dataset always brings those fields as null. Here is the list of fields:
I used an API token associated with my account, which has limited access to Jira. However, I checked my Jira, and I can list the issues and see those fields, so maybe it’s not a Jira permissions issue?
Hi @albmargar ,
So considering that there is some missing data in the dataset that results in a null value and you can access this data in Jira. It’s not a permission issue but might rather require you to do data cleaning or transformation through services such as AWS Glue and Amazon Athena.
Based on the missing fields that you have shared, I wanted to ask if these are nested in one another, if so then you might need to use the data transformation route that I mentioned above, since the data is organized in a heirarchal manner in Jira.
Please let us know if you have additional questions or concerns on this.
Hi Sabbahh, thanks for your response! I don’t have experience with Jira’s hierarchical structure, but it seems strange to me that this would be the cause of the error. Two of those three fields are directly related to the Jira issue in a 1:1 manner (except for Sprints, where a single issue could have N related sprints). However, if I can see the field creation date, shouldn’t the story points and the related epic be at the same hierarchical level?
Do you know where I can see the hierarchical structure of Jira?
Edit: Regarding the Sprints field, I found that Labels should behave similarly since an issue can have multiple Labels, and these fields are correctly captured by the API!
Hi @albmargar
Glad to hear that you were able to correctly capture the labels from the API for the Sprints field!
If the three feilds are directly related in a 1:1 manner then it might not be a hierarchical level issue, especially considering that you can pull out the issue creation date. @salim might be able to suggest a better way to approach this as well, so i’ll include him here in this thread as well.
In regards to see the hierarchal structure in Jira, for you projects if you change it tab to the “List” format you can see if data is nested such as this screenshot below. We have an epic type with 3 different stories nested under it.
I understood what you meant about the hierarchical structure!
Just to clarify, I couldn’t capture the Sprints field. I captured the Labels field, which I believe has a similar structure to Sprints (a list of strings)!
Edit: I just watched your YouTube video again and noticed that the fields I mentioned (Sprints, Story points, etc.) are not used in the dashboard example. Could there be an issue with integrating those fields at the moment? Could you confirm whether you have values on those fields in your Jira dataset?
Hi @albmargar,
It’s been awhile since last communication on this thread, did you have any remaining questions or were you able to find a work around?
If we do not hear back within the next 3 business days, I’ll go ahead and close out this topic.
Thank you!
Hi @Brett,
I’m still experiencing the issue: some fields in my datasets are always null, even though values have been set in Jira.
Is there anything more I can try, or could there be an issue with the Jira integration in QuickSight?
Hi @albmargar,
Have you explored this article?
While I don’t have a lot of experience working with Jira, if you’re still receiving nulls, I believe the best route would be what Sabbahh suggested earlier by utilizing Glue or Athena.
One additional route you can explore would be to create a support ticket, the AWS support team may be able to assist further as well!
Hi @Brett,
I’ll explore other solutions, but it feels strange to me that the Jira API integration with QuickSight doesn’t support those fields.
Hi @albmargar,
Agreed that it is a bit strange, I’ll mark this as a feature request as well to promote visibility to the AWS support team!
