[Feature] Jira Source Package - Field History "Is Active" support

[alastairbulloch]

Is there an existing feature request for this?

• I have searched the existing issues

Describe the Feature

Fivetran's Jira Connector added a new "IS_ACTIVE" column to the ISSUE_FIELD_HISTORY table which (I believe) shows which of the field's history values is the current one.

Can we add this to the Jira Source DBT package so that we can use this column downstream?

It's a much more efficient way of determining the current value for custom fields etc.

Thanks,
Ali

Describe alternatives you've considered

I'm going to manually join the DBT source package issue field history model with a homebrewed model that patches in that field...

Are you interested in contributing this feature?

• Yes.
• Yes, but I will need assistance and will schedule time during your office hours for guidance.
• No.

Anything else?

Keep up the good work :)

[fivetran-joemarkiewicz]

Hi @alastairbulloch thanks so much for opening this feature request!

I think this feature request is a very relevant addition to the package and will help with performance of the package to take advantage of this new field as opposed to recreating the field as we currently do in the package code. I will need to do some investigating in order to understand if adding this logic in the connector was rolled out widespread, or just to new connectors.

Nevertheless, we will explore this during the next major update to the Jira package to help with performance. Thank you again for the great suggestion!

[elyalvarado]

This should also be added for the ISSUE_MULTISELECT_HISTORY table, which suffers from the same problem

[zoraida]

Is this issue going to be fixed?

[fivetran-joemarkiewicz]

Hi all, we are actually planning on developing a new feature for the Jira package in the current quarter that somewhat aligns with this feature request. We'll take a closer look at this feature to determine if it will integrate well within the updates we're planning. We'll share more details in the coming weeks if something we'll be able to support.

[afranzi]

Hello, it would be great to address this issue sooner, otherwise, we end up showing not accurate data in these models.

Thank you team!

[fivetran-avinash]

Hi @afranzi , we are actually working actively on this feature, but just curious, could you explain why are you not getting accurate data? While adding the is_active flag will be helpful for filtering your data, we are only adding the is_active field, not filtering out the inactive records. Did you mean it'll be easier for you to query and filter on the active records?

[afranzi]

Hi Avinash, exactly, we can not filter out non active records, so we have issue labels that should be removed from issues still showing up in the models since we cannot remove them when using this dbt package.