Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Missing Story Points Columns in Jira Quickstart Data Model – sys_jira_core_jira

Answered
Yue Wu User

Hi Fivetran Support Team,

I'm writing to report missing columns in our Jira Quickstart data model that are causing failures in our downstream transformations.

---

CONNECTOR DETAILS
- Connector Name: sys_jira_core
- Connector Type: Jira
- Destination: Snowflake (Snowflake_PRODUCTION)
- Transformation Type: Quickstart

---

ISSUE SUMMARY

Several story points-related columns that were previously present in the Quickstart model source tables are no longer available. Our downstream snapshot models reference these columns, and their absence is causing transformation errors.

We believe this is the result of a recent schema change on the Fivetran Jira connector side, where these columns were either removed or are no longer being populated.

---

AFFECTED MODELS & MISSING COLUMNS

1. Snapshot: CLEANSED_JIRA__DAILY_ISSUE_FIELD_HISTORY_SNAP
   Source Table: JIRA__DAILY_ISSUE_FIELD_HISTORY
   Missing Columns:
   - STORY_POINTS
   - STORY_POINT_ESTIMATE

2. Snapshot: CLEANSED_JIRA__DAILY_SPRINT_ISSUE_HISTORY_SNAP
   Source Table: JIRA__DAILY_SPRINT_ISSUE_HISTORY
   Missing Columns:
   - UPDATED_AT
   - STORY_POINTS
   - STORY_POINT_ESTIMATE

3. Snapshot: CLEANSED_JIRA__ISSUE_ENHANCED_SNAP
   Source Table: JIRA__ISSUE_ENHANCED
   Missing Columns:
   - STORY_POINTS
   - STORY_POINT_ESTIMATE

4. Snapshot: CLEANSED_JIRA__SPRINT_ENHANCED_SNAP
   Source Table: JIRA__SPRINT_ENHANCED
   Missing Columns:
   - STORY_POINTS_COMMITTED
   - STORY_POINT_ESTIMATE_COMMITTED
   - STORY_POINTS_END
   - STORY_POINT_ESTIMATE_END
   - STORY_POINTS_COMPLETED
   - STORY_POINT_ESTIMATE_COMPLETED

---

QUESTIONS

1. Were these columns intentionally removed from the Jira Quickstart model in a recent update? If so, could you point us to the changelog or release notes?
2. If this was unintentional, what is the expected timeline for restoring these columns?
3. Is there a recommended workaround to retrieve story points data from the raw source tables in the interim?

---

These missing columns are causing downstream model failures and impacting our reporting. We'd appreciate a prompt response.

Please let me know if you need any additional information.

Thank you.

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Official comment
    Joe Fivetranner

    Hi Yue, thanks for creating this feature request. To address your questions directly:

    1. Were these columns intentionally removed from the Jira Quickstart model in a recent update? If so, could you point us to the changelog or release notes?

    • This was an intentional change to the Jira Quickstart model. This change was introduced within the v1.4.0 update to the Jira Quickstart data model. These fields were removed by default as they are not always available.

    2. If this was unintentional, what is the expected timeline for restoring these columns?

    • At this moment we don't plan to bring them back in as default fields. However, you can add them to the "Issue Field History Columns" variable so they may be included as they were before.

    3. Is there a recommended workaround to retrieve story points data from the raw source tables in the interim?

    • Yes, you will be able to add these fields back to your end models by taking the following steps:
    1. Navigate to your Jira Quickstart data model in the Fivetran UI
    2. Select the "Settings" tab
    3. Add to the "Issue Field History Columns" variable a new record for "Story Points", "Story Point Estimate", and any other fields you would like to track
    4. Re-run your Quickstart data model with full refresh
    5. The story point related fields will be tracked again in the end models.

    Let me know if the above steps bring back the fields as you had expected them before. Thanks!