fix(reconcile): jira staging dbt selector matched zero models (tag:jira-staging)

[mitasovr]

Problem

On virtuozzo, nightly jira syncs were green end to end (sync → enrich → silver all Succeeded) yet the jira dbt data was frozen for ~2 weeks:

• staging.jira_issue_field_snapshot = 0 rows
• staging.jira_changelog_items frozen (2.9M, last touched by a manual run)
• silver.class_task_field_history (ephemeral, reads changelog_items) frozen at the last manual run's date
  while bronze_jira.* was fresh daily.

Root cause

The jira enrich pipeline runs three dbt phases: staging → enrich → silver. Both renderers — render_sync_trigger.py and render_cronworkflow.py — hardcode the staging selector as tag:jira-staging for jira:

dbt_select_staging = "tag:jira-staging" if args.connector == "jira" else ""

No model carries the tag jira-staging. The two jira staging models are tagged ['staging', 'jira']:

• jira__changelog_items.sql
• jira__issue_field_snapshot.sql

So dbt run --select tag:jira-staging selects zero nodes, exits 0 with "Nothing to do", and the step goes green while building nothing. enrich and silver then run on empty/stale staging.

Manual run-sync.sh uses DBT_SELECT_STAGING="tag:jira" — which is why manual/local runs populated the tables but reconcile-rendered cronworkflows never did.

Fix

Select tag:staging,tag:jira (intersection) in both renderers — exactly the two jira staging models, nothing broader. Verified against the models' actual tags and that no model is tagged jira-staging.

Rollout

App-repo change → toolbox build → reconcile re-renders the cronworkflows with the corrected selector. After that the nightly staging step rebuilds changelog_items + issue_field_snapshot, and the downstream silver unfreezes.

Context: this is the dbt-layer half of the jira recovery on virtuozzo. The ingestion-layer fixes (substream cache #1283, concurrency #1308, descriptor bumps #1310, global cursor #1370, cursor formats #1383, airbyte-server memory in gitops) are separate and already landed/deployed; bronze is fresh — only the transform layer was stuck, on this selector.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Bug Fixes
  • Corrected data model selection logic for the Jira connector to ensure staging models are properly targeted during nightly synchronization workflows.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ee204017-4862-4762-a22b-9eac645acf01

📥 Commits

Reviewing files that changed from the base of the PR and between d0775ac and 66a1156.

📒 Files selected for processing (2)

• src/ingestion/reconcile-connectors/python/render_cronworkflow.py
• src/ingestion/reconcile-connectors/python/render_sync_trigger.py

---

📝 Walkthrough

Walkthrough

Two Python render scripts (render_cronworkflow.py and render_sync_trigger.py) each had a jira-connector branch that set the dbt staging selector to the non-existent tag tag:jira-staging. Both are corrected to use the intersection selector tag:staging,tag:jira.

Changes

Jira Staging Selector Fix

Layer / File(s)	Summary
Fix DBT_SELECT_STAGING for jira connector src/ingestion/reconcile-connectors/python/render_cronworkflow.py, src/ingestion/reconcile-connectors/python/render_sync_trigger.py	The jira-specific branch in both scripts now sets the staging dbt selector to tag:staging,tag:jira instead of the previously used tag:jira-staging (which matched no models). Non-jira connectors continue to receive an empty selector.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐇 Hippity-hoppity, tags gone astray,
jira-staging led models astray!
Now comma-joined, intersection neat,
staging and jira finally meet.
The rabbit fixed it — hip hip hooray! 🥕

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main bug fix: correcting the jira staging dbt selector from the incorrect non-existent tag 'tag:jira-staging' to the correct intersection 'tag:staging,tag:jira'.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}