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

Community

Connector Improvement: _fivetran_deleted field/feature for all Jira/JaaS dimension tables such as `status`, `components`, `versions` and more

Answered
Charlie Cao User

When querying Jira/JaaS history, there are historical updates/entries that contain values which no longer exists in the dimension/lookup table because of updates or deletions--this results in unknown field value names and break the foreign key and primary key relationship between the history fact table and the field value dimension tables. This problem exists for fields such as `status`, `components`, `versions`, and more.... It would be great if all fields can have the `_fivetran_deleted` flag enabled so that no historical data is lost.

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Official comment
    Erin Fivetranner

    Hi Charlie - 

    Thanks for submitting this request. I believe what you are describing is History Mode in Fivetran where we track each iteration of a record from the source as it's own row. Is that what you are you looking for here? 

    Can you also share a bit more about your use case here for historical tracking in Jira? 

    Thanks, 

    Erin 

  • Charlie Cao User
    • Edited

    Hi Erin,

    Thanks for following up and apologies for the late reply!

    1. It doesn't seem like "History Mode" is available for Jira connectors yet according to this page? 
    2. Below screenshot shows an example of our historical analysis, where Status change histories were needed, but Statuses that no longer exist in the `status` dimension table cannot be looked up.
    3. We noticed that the Jira API itself does capture both the ID and the Value of historical changes (instead of only containing the ID and having to look up the Value from dimension tables). Is there anyway we could capture the `toString` field under `items` in `changelog`?