Skip to main content
📢 Syncs times may take longer than usual during major retail events, such as Black Friday and Cyber Monday due to an increase in activity and larger data sets. For any other issues, please visit our Status Page or contact our Support Team.

Community

Connector Improvement: Jira - Filter to specific projects

Completed

Please sign in to leave a comment.

Comments

5 comments

  • Official comment

    Hi Cliff. Our goal is to keep the connectors easy to configure and as a result our users need to do any filtering on the data warehouse side. A good option for you is to create a database view that filters out those specific projects and then only make that view available to your end users, not the original table. 

    Hi Cliff, another option here is to restrict Fivetran's permissions so we can only read projects you determine are valuable to pull into your warehouse. Some of our other customers have been successful with this method.

    We also have the need for a filter on JIRA.  We have over 90k issues logged in JIRA that go back over 10+_ years.  We do not need to pull all of that data.  The history on all of those issues is over 100million records in the ISSUE_HISTORY_FIELD table in out Data Warehouse.  Fivetran will take months to move all of that data.  If we could add a filter ID under an Advance tab on the connection screen, that would help us limit which issues we move with Fivetran. 

    Hi Anna,

    > to restrict Fivetran's permissions so we can only read projects you determine are valuable to pull into your warehouse.

    Do you know how can I configure this?

    Hi All - Apologies for the late late update on this! We started supporting this feature a few months back! You can select your projects now from the setup form. 

    Best,

    Erin

Didn’t find what you need?

Contact support