Jessie Turpin Atlassian Team

Comments

  • You're welcome, @Don DMack! Let us know if you run into any issues when you try it out. 
  • Hi Dave! Thanks for the question. It is possible to have one dashboard with multiple controls that are not connected to every chart on the dashboard. If you have created your controls to Automatically connect to new and existing charts then you'll need to remove that automatic control filter in any charts that you don't…
  • 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! 
  • 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. It's possible that your query may be using the Creator or Reporter account ID instead, which could explain the incorrect…
  • Hey Matthew! It sounds like your "In Review Statuses" is a Dropdown control. If you'd like to learn more about how the control was created, and which data is selectable within the control, you can edit the control. Editing the control allows you to see which column is used and if any additional steps are used to transform…
  • Hey Magdalena! This article should be able to help you remove the user's Statuspage Product Admin access. Just note that instead of granting the user access like the article's instructions have, you'd be doing the opposite steps and removing the user's access. If you run into any issues and need additional help, opening a…
  • Hey Chhaya! I just checked the feature request, STATUS-96, and it hasn't been released yet. The engineering team is still gathering interest, and I've marked your question here as interested in seeing the feature implemented. Feel free to reach out via support.atlassian.com if you want more information or have other…
  • You're welcome, Shraddha! Here is a link to our documentation on the different control types available. The Date slider control is similar to the Calendar control, but one difference is you can select a specific column to be used to create the control. One caveat with using the Date slider control is that the data will…
  • Hi Shradda! Currently, you won't be able to restrict users from selecting a date in 2014 in your Calendar control. Though you can edit the default start and end dates in your Calendar to be the default dates filtering your charts. You can either use a fixed date (2024-03-04) or a relative date using one of our relative…
  • Hi Matthew! Thanks for posting your question and sharing the screenshot. Locked fields are currently unavailable in the Atlassian Data Lake, but we have a feature request that you can watch for updates on when these fields might be available to query. Hope that helps!
  • Hi Jakob, To find the assignee of an issue, you can use the Assignee account ID column from the Issue table. Note that if your organization is a managed account, the Account table 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…
  • Hi Mary! When creating a custom column in your data source's schema you won't need to include typical SQL statements like SELECT, FROM, etc because the custom column can only be created from a column that already exists in that specific table. You can read more about the settings of a custom column and see an example in…
  • Hi Richard! We have a feature request for project status data to be added to the Atlassian Data Lake. Having a project's status included would allow you to filter out any inactive projects. In the meantime you or one of your organization admins can edit your Atlassian Data Lake connection to unselect any projects that have…
  • Hi Graham! The third example (the number of objects with a particular attribute) in this Knowledge Base article should be able to help you adjust your query. Step 2b in the article will be where you add in a filter on your specific 'Status' attribute to help you get a count of Apple devices per status. I hope this helps,…
  • Hey Shraddha! Based on the additional information you commented on a different question, here's how you could update your existing chart to get your desired result. I think you could modify your Query 3 to include the filter on Issue type to only have Story or Epic issues displayed. This would allow Query 3 to give you the…
  • Hey Shraddha! I'll respond on the Community question you initially posted just in case anyone with a similar question will see how to create the chart.
  • Hi Shraddha! Standard and custom Jira field data can be found in the Issue field table. You can follow the instructions on this knowledge base article on how to query your custom fields. 
  • Hey Stacey! If I had to take a guess about why you're getting no results after merging the two queries together, I'd say it's probably due to the rows where two or more users have been selected in your field. This would be because the Account ID column from the Account table is expecting only one account ID, but some rows…
  • Hey Adam! Thanks for the suggestion. As you've noticed Forge data isn't supported in the Atlassian Data Lake, so I created a feature request on your behalf for this data. Feel free to vote for and watch the feature request to informed on any future updates. Let us know if you have any other questions or suggestions! 
  • Hey Yavor, Looking at this again, I think you'd need to swap out the Created at and Resolution at columns that are grouped by seconds and instead use the Started at and Stopped at columns from the SLA table. You'll need to group the Started at and Stopped at columns by seconds as well. Note that you'll need to edit some of…
  • Hi Yavor! You could make a copy of the Time to resolution chart on the Request management overview dashboard template. Then in your copied chart you could add a query filter where the SLA name = Time to first response. The screenshot below is an example of what the modified query could look like. Let me know if you have…
  • Hi there! If your organization is a managed account then the Account table of the Atlassian Data Lake schema would hold the names of the users selected in your People custom field. To add those names to your query, you would need to add a second visual mode query with the Account ID and Name columns from the Account table.…
  • Hey Piotr! Although some Jira sprint fields can be queried within the Issue field table, the results won't yet be able to be mapped to the actual values found in Jira. We've got a feature request ticket for sprint data to be added to the Atlassian Data Lake that you can watch for updates. Once that data is added you'll be…
  • Hi Diego! If you'd like to have the custom fields be their own columns and don't want to create one query per custom field, you could consider creating custom columns in the Issue field table. This would allow you to use fewer queries in your chart while also having each custom field be a column. Here is an example piece…
  • Hey Piotr! Would you mind creating a support ticket and select Atlassian Analytics as the affected product. This would allow our team to investigate further why your data isn't appearing in the Atlassian Data Lake. Thanks! Jessie
  • Hi Krzysztof! Text input controls require an exact string match, so you'd need to type out the issue summary completely within your control to have results returned by your query. However, you could use the % wildcard with your control to use a partial string match, which would function similar to the JQL contains. This…
  • Hi Jonathan! This isn't directly possible within the Jira integration with Opsgenie. However, you could setup the integration using the Opsgenie Edge Connector (OEC). Using the OEC you can customize the script to assign the team the ticket in Jira. Another approach would be to utilize automation rules within your Jira…