Have certain types of JIRA issues flow into Collibra using WebHooks
Overview
During the life cycle of a ticket in a ticketing tool such as Jira, ServiceNow, etc., the ticket may be deemed to be caused by a structural data issue. In such a case, you may need the data team to handle it in Collibra. Examples of structural data issues include but are not limited to:
- data not arriving to a destination in a timely fashion
- incorrect or out-of-date reference data being used in an application
- crippling data quality issues causing disruptions in business.
You may need to handle such issues in Collibra as they typically fall under the responsibility of the Chief Data Officer. You should document and communicate about the issues transparently to make other people in the organization who rely on the underlying data aware of such issues. For example, it would be very useful for a risk data analyst to be aware of structural data issues as they investigate the lineage of a data set in Collibra. This way, they can take into account the potential data accuracy issues in their SQL queries.
This integration demonstrates how you can implement a flow of issues between Jira and Collibra. You can adapt this integration to achieve the same with other ticketing and service desk tools.
Elements in Scope
- Collibra domain: Jira Structural Data Issues
- Asset type used by integration: Issue
To receive support on this item, you can engage our Professional Services team or post any questions in the Data Citizens Community.
Media
More details
Release Notes
- Removed security vulnerabilities
- Upgraded to Spring Boot version 2.7.5
- Docker file added
Compatibility
- Spring Boot Framework
- Eclipse IDE
- Collibra Data Intelligence Cloud
- Collibra Data Intelligence On-Prem
Dependency
- Java Runtime Environment 1.8
- Spring Boot Integration Library
- Collibra Data Intelligence Cloud API v2
License and Usage Requirements
Release History
Release Notes
- Updated the Spring Boot Starter Parent version to 2.5.12
- Updated the Collibra Integration Library version to 1.1.5
Compatibility
- Spring Boot Framework
- Eclipse IDE
- Collibra Data Intelligence Cloud
- Collibra Data Intelligence On-Prem
Dependency
- Java Runtime Environment 1.8
- Spring Boot Integration Library
- Collibra Data Intelligence Cloud API v2
License and Usage Requirements
Release Notes
– Refactoring according to standard-reference template.
– File Structuring of Components and Services
– Constructor Autowiring
– Adding Constants
– Fixing Type Warnings
– Exception Handling
– Lombok
– Sync Lock
– Adding AppConfig
– Updating Authentication Config
– Main Service with ETL format
Compatibility
- Spring Boot Framework
- Eclipse IDE
- Collibra Data Intelligence Cloud
- Collibra Data Intelligence On-Prem
Dependency
- Java Runtime Environment 1.8
- Spring Boot Integration Library
- Collibra Data Intelligence Cloud API v2
License and Usage Requirements
Release Notes
Initial release:
Spring Boot integration designed to read data and receive request from a specified JIRA instance, transform it, and then upsert it to a Collibra Platform instance as assets.
Compatibility
- Spring Boot Framework
- Eclipse IDE
- Collibra Data Intelligence Cloud
- collibra integration library
Dependency
- Java Runtime Environment 8
- Collibra Data Intelligence Cloud API v2
- Collibra Platform v2021+
- Spring Boot Integration Library
License and Usage Requirements
See existing Q&A in the Data Citizens Community
Browse discussions with customers who also use this app.
Start a New Topic in the Data Citizens Community
Collibra-hosted discussions will connect you to other customers who use this app.
The following terms shall apply to the extent you receive the source code to this offering.
Notwithstanding the terms of the Binary Code License Agreement under which this integration template is licensed, Collibra grants you, the Licensee, the right to access the source code to the integrated template in order to copy and modify said source code for Licensee’s internal use purposes and solely for the purpose of developing connections and/or integrations with Collibra products and services.
Solely with respect to this integration template, the term “Software,” as defined under the Binary Code License Agreement, shall include the source code version thereof. Except with respect to the foregoing, all remaining terms of the Binary Code License Agreement shall apply to the license of integration template hereunder.
