Jira#
Connect Jira with an email address, tenant domain, and API token. The source writes 23 core tables plus discovered custom fields under titan.jira.
Connect Jira#
Open Apps, choose Connect app, and select Jira.
Enter an email address, tenant domain, and API token.
Review the tables, then save the source.
Watch Sync history until the first run completes.
Credentials are stored as secrets. They never become lake columns or appear in query results.
Sync behavior#
Issue custom fields expand into typed columns and supporting tables. A source-domain collision stops setup instead of mixing tenants.
A new source syncs when you connect it and then follows its schedule. The default recurring interval is 4 hours. An interrupted run keeps its completed progress and retries safely.
Every lake table also has the system columns _synced_at and _deleted; the column reference below lists source columns only.
Table reference#
Supernova discovers this reference from the connected account. Jira field metadata defines custom columns. Issue links, sprints, comments, and multi-select values become related tables.
Open Apps → Jira → Tables after the first discovery run to see every exact table name, column name, type, and sync selection. Dynamic fields cannot be listed truthfully before an account is connected.
Deletes and history#
Rows are merged by their source key. When the source can prove that a row was deleted, Supernova keeps the row and sets _deleted so queries can choose whether to include history. Filter current-state queries with where not _deleted.