Comments
-
From the looks of your screenshot, it appears that the field you are trying to find the null values for is a custom field that is present in the Issue Field table. This table only has rows for values that ARE present and does not contain "empty" or null rows for issues that do not contain a value. The way around this is to…
-
Hi Dusan, I believe your 5th column is what is causing the duplicate rows. You want to change that aggregation to SUM (or something other than group) so that they rows are combined. If you run into any more issues with this, feel free to open a support ticket and we can continue the conversation, in depth, there.
-
Hi Dusan, I do not have a custom field called "Project ID" to mock up an example with, so I used a different custom field called "Priority", you can use the same approach, but instead use your project ID field. You can see I can accomplish this with a single visual SQL query and then a few follow up steps. I hope this…
-
Hi Andrew, you could query the Issue History table for this information. This will store a historical record of all field changes. If you query the table for the field name assignee, you will be able to perform a count of issues assigned to users. Here is a very basic approach to begin looking at that information:
-
Hi Sebastian. I think what you are after would require to queries. The first query to define what parent issues you actually wanted to include and the second to include the filter. In my attached example you can see that I am creating a chart to display all children of a specific issue (In this case PT-6181) If this isn't…
-
Hi Shraddha, Some of this missing Sprint data may be attributed to the ongoing incident affecting the Atlassian Data Lake. If you are suspecting you are experiencing data discrepancy issues, please open a support ticket here and set the affected product to 'Atlassian Analytics.' With regards to your approach, it looks like…
-
Hi Steven, This is occurring because you have selected unaggregated for Issue ID but have selected group as the aggregation for "value", those columns will also need to be unaggregated. Also, if you run into any more issues on this chart, please feel free to open a support ticket…
-
Hey Steven, In both queries Issue ID would have to be unaggregated because you need both queries to return the issue id's themselves so that you can join on them. If you want to get counts, you can add a Group & Aggregation step at the end of everything else.
-
Hey Steven, Instead you can apply that filter in the Custom Field query and by using an inner join instead of a left join. So, in your query where you are returning Contract Orgs, you can add a filter for value is one of (Org1, Org 2, Org3) Then by changing to an inner join only rows where the value matches is one of…
-
Hi Steven! Thanks for your question. You're on the right track with regards to setting up a filter with the Name and Values for the custom fields in the Issue Field table. You can read more about that filtering here. The trick is that each custom field you wish to add to your result set, will need to be it's own query. You…
-
The supported third party data sources include: * Amazon Athena * Amazon Aurora * Amazon Redshift * Google BigQuery * Microsoft SQL Server * MySQL * PostgreSQL * Snowflake You can learn more about connecting to third party data sources here
-
So I started looking at this, and I believe I have come up with a solution. It looks like the "value" for the Issue Link field will be the "Issue Ref" value of the Issue. I have created what I hope is what you're after: Let me know if you have any questions or concerns with this approach.
-
Currently there is not a way to map Atlassian user ids to actual user names because the required user data is not yet available in the Data lake. The process of getting this data into the lake is ongoing and we hope to have that user data in the data lake soon.
-
When creating your {LABELS_DROPDOWN}, a good approach would be to ensure you're creating a dropdown with all of the potential labels. To create a dropdown control of all the labels you can simply select the "Labels" column from the Jira Issue table and then use the "Explode" aggregation. You will then need a "Group &…
