Connector Improvement: Implement table level sync for the jira connector
AnsweredIn https://support.fivetran.com/hc/en-us/requests/359462 we're facing an issue where we're missing some older tickets in the table, and the only way to solve this is to do a full resync for the connector. The sync is estimated to take 1-2 weeks, which is too long a period to go without updated jira data.
We'd like some way for scoping down the full resync.
1. (Preferred) Triggering a historical resync scoped to one or more selected projects, leaving other projects' incremental syncs uninterrupted.
2. Implementing table-level resyncs for jira. This is less than ideal, but it might be useful if the resync times are much smaller when only a subset of tables is selected. This would also involve a lot of manual work on our side, which we'd prefer to avoid.
-
Official comment
Hi Suraj,
Thanks for submitting this request. Our team will take a look into this and get back to you.
We will keep this thread updated with any progress.
Thanks,
Frank -
Hi Team,
Do we have any update on this ticket?
-
Hi,
We are planning to add table level resync for JIRA in the coming months. We are not planning to support project level resync for the time being, but please continue to upvote this post and we will prioritize by demand for this feature.
Thanks,
Frank
Please sign in to leave a comment.
Comments
3 comments