Hello, Running into an issue with incremental state working as expected. I am using the --state-id flag and can see the replication key and replication value being set as expected in the state information, but the runs seem to be ignoring this value. I am attempting to use an updated_at date, but I am still seeing all records being synced on subsequent runs. Here is my Meltano config and state. I am using

tap-jira

and focused on the Issues stream:

metadata:
      issues:
        replication-method: INCREMENTAL
        replication-key: updated_at

State:

Incremental state: {'bookmarks': {'audit_records': {'replication_key': 'created', 'replication_key_value': '2024-01-04T22:44:49.075+0000'}, 'fields': {'replication_key': 'id', 'replication_key_value': 'workratio'}, 'issue_types': {'replication_key': 'id', 'replication_key_value': '10213'}, 'issues': {'replication_key': 'updated_at', 'replication_key_value': '2024-01-04T22:44:49.204+0000'}, 'issue_changelog': {}, 'issue_comments': {}, 'issue_watchers': {}, 'issue_worklogs': {}}}

Am I missing something here? Since the State for the job seems to be recording the replication-key-values correctly, I would not be expecting to see records synced with an updated_at date earlier than this value in the case of the Issues stream.

Hi Nick! The stream implementation seems to be missing the code for actually using the replication key to filter values. The endpoint seems to accept a

from

param: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-audit-records/#api-rest-api-3-auditing-record-get So, we'd need to override

get_url_params

to make use of

get_starting_timestamp

and pass it as the

from

query parameter.