JIRA Changelog - Snowflake
The JIRA Changelog Kit pulls data from multiple JIRA entities and creates a historical changelog for the JIRA issues and an issue table with custom fields as columns. This Kit uses Rivery’s predefined reports functionality to retrieve the JIRA entities issues, issue fields, projects, users, groups, group users, and resolutions. To add additional entity reports, the user can just select more in the schema section of the “Jira – Source Reports” river. The SQL logic flattens the results from the issue table to create the output tables.
This Kit includes…
- Data ingestion from the following JIRA entities:
- Logic that orchestrates the transformation of the historical JIRA changelog and the custom fields issue table.
Minimum RPU Consumption: 8
Configuring this Kit for use
Variables
In this Kit, there are three variables that are used to make for dynamic use of target configuration.
- {Database_Jira} is used in all Target configurations and queries as the target database name.
- {Schema_Jira} is used in all Target configurations and queries as the target schema name.
- {Jira_Alert_Group} is used as the alert email address(es) for when a river fails (optional).
Go to the Variables menu on the left side navigation bar and create variables for Database_Jira, Schema_Jira, Jira_Alert_Group, and Jira_Alert_Group. Fill in the values as the Snowflake database and schema where you would like the data to land and the email address(es) to which you would like the failure emails sent.
Connections
Kits are imported with ‘blank’ source and target connections. In order to use the kit, you have two options:
- Swap out blank connections with existing connections
- Add credentials to the blank connections that come with the imported Kit
Have questions about this Kit?
Set up a meeting with a Rivery solutions engineer.
