How Does the ETL for Reporting App Report Jira Changes?
Event triggered automatic reporting
Once a Data ETL rule has been created by the Jira Admin, the app starts the reporting of Jira changes based on these rules:
If the end user creates an issue in a project matching the rule, the app inserts immediately a corresponding row in the reporting table
Every custom or system will be stored as a column in the reporting table
If the end user changes an issue in a project matching the rule:
If the database row already exists, the app updates the reporting table
if the database doesn’t exist, the app creates a corresponding row in the reporting table
When the rule is created and several issues matching the rule exist in the system, the admin can make a bulk change of the issue (e.g., add a Label and then remove it) to store all previous issues in the reporting table.
Created reporting tables
The tables created by the app should NOT be changed by DB Admins to ensure a correct operation.
The following technical columns always exist for every reporting table:
id: technical IDs of Jira issues
serverid: the unique Jira server ID
vip_lean_ver: version of the app
row_created: timestamp set by the app after creation
row_updated: timestamp set by the app after update