Manage the Jira Connector

This applies to: Visual Data Discovery

The Symphony Jira connector lets you access the data available in Jira. Obtain the connector server following this process: Obtain Additional Connector Servers

After the connector has been set up, you can create data source configurations that specify the necessary connection information and identify the data you want to use. See Manage Visual Data Discovery Data Source Configurations for more information. After data sources are configured, they can be used to create dashboards and visuals from your data. See Create Data Discovery Dashboards.

Symphony Feature Support

Connector support for specific features is shown in the following table.

Key: Y - Supported; N - Not Supported; N/A - not applicable

Feature Supported?
Admin-Defined Functions N
Box Plots Y
Custom SQL Queries Y
Derived Fields (Row-Level Expressions) Y
Distinct Counts Y
Fast Distinct Values N
Group By Multiple Fields Y
Group By Time Y
Group By UNIX Time Y
Histogram Floating Point Values Y
Histograms Y
Kerberos Authentication N
Last Value N
Live Mode and Playback Y
Multivalued Fields N
Nested Fields N
Partitions N
Pushdown Joins for Fusion Data Sources N
Schemas Y
Text Search N
TLS N
User Delegation N
Wildcard Filters Y
Wildcard Filters, Case-Insensitive Mode Y
Wildcard Filters, Case-Sensitive Mode Y

Connect to Jira

To connect Symphony to your Jira instance, provided the JDBC url, a Jira user name, and password or API token.

Input Field Description
JDBC Url jdbc:jira://;Host=host_name_or_your_server;Auth_Type=Basic Authentication
User Name Jira user name
Password Jira user password or API token generated for the Atlassian account.

Configure your Jira rate limit using Atlassian's guidelines to minimize rate limit errors and prevent performance issues. Rate limit are configured per user, per project; add a test user account with no rate limit to test your projects. See https://developer.atlassian.com/cloud/jira/platform/rate-limiting/.

Optimize Performance

The Jira connector and Simba JDBC driver use schema tables to map your data to a compatible JDBC format you can use when creating your sources. Learn more here: Schema Tables.

Custom SQL Optimization

Large Jira boards and projects can affect the connector's performance. To minimize this impact, you can create your data source using a custom SQL query and pushdown filters. To optimize the query, you can:

  • Include pushdown filters

  • Design queries to filter on columns for which folding is supported

  • Limit your query using a WHERE clause and TOP for columns that don't support pushdown filters

  • Narrow your data retrieval by filtering your data by epic, project, issue creation date, or completion date

  • Speed your initial load time by defining a small time range on the Global Settings tab

Example:

SELECT S.Sprint_name, S.Sprint_startDate, S.Sprint_endDate, S.Sprint_state, I.Issues_fields_project_name, I.Issues_fields_project_key, I.Issues_fields_status_name, I.Issues_key
FROM Agile_Board_Sprint S
JOIN Extra.Agile_Board_Issue I ON S.Sprint_id = I.Issues_fields_sprint_id
WHERE S.Sprint_startDate > 'YYY-MM-DD' AND I.Issues_fields_project_key = 'MY_PROJECT_KEY'

Raw Data Cache

You can reduce the number of queries Symphony makes to the source and speed up data query execution by enabling raw data caching. When enabled, an Entity Data Cache toggle is added to the Source Creation work area. Enable and define a caching schedule. Contact Technical Support for assistance enabling this feature.

Custom Fields

See Api_Field for custom fields mappings. The field custom_name is type SQL_VARCHAR(1024) and is often represented in JSON format. Use the SUBSTRING() function to extract fields from the JSON.

Example:

SELECT Fields_Issue_Type_Name, SUBSTRING(customfield_13218, 89, 5) AS Team, SUBSTRING(customfield_11200, 105, 1) AS Severity, Fields_Status_Name AS Status, SUBSTRING(customfield_12618, 105, 8) AS Defect_Origin, Fields_Created, customfield_10100 AS Story_points
FROM Extra.Api_Issue E
WHERE Fields_Project_Key = 'MY_PROJECT_KEY' AND Fields_Issue_Type_Name = 'Story'

Retrieving and Calculating Story Points

Jira stores time estimation and story points. The story points are a custom field mapping, see Api_Field. Use this information to build custom metrics and return commonly used calculations.

  • Committed story points: SUM(story_points)

  • Completed story points: SUM(story_points) WHERE fields_status_name = 'Done'

  • Percent completed: (SUM(story_points) WHERE fields_status_name = 'Done') / (SUM(story_points))

Example:

SELECT Issues_fields_project_name, Issues_fields_sprint_name, Issues_fields_sprint_startDate, Issues_fields_sprint_endDate, Issues_fields_sprint_self, Issues_fields_sprint_state, Issues_key, Issues_fields_status_name, customfield_10100 AS story_points
FROM Extra.Agile_Board_Issue
WHERE Issues_fields_project_key = 'MY_PROJECT_KEY' AND Issues_fields_sprint_name !=NULL