I went through the code but was not able to exactly point out where the filter is being applied. I see that there is a for loop in rest stream sdk (https://github.com/meltano/sdk/blob/1f62ae45888e908bc93afd1b8e047288deb2f964/singer_sdk/streams/rest.py#L127) which is responsible to take the config and put it in url but not sure if it is working,

I am able to list all issues via the api using jql correctly

https://github.com/MeltanoLabs/tap-jira/blob/eb808ba5f24e51d0acfafa91dc3deaac63e8d121/tap_jira/client.py#L74 I think if we add a

param['jql'] = urlencode("updated>=self.config['start_date] and updated<self.config['end_date']")

here might work

let me know if I can open an issue

realized don't have to urlencode and made it work

can also have a parameter or setting for

jql

in the config itself would be a nice addition

realized can just put

def get_url_params

in the

IssueStream

itself, also working as expected 🚀

realized that the IssueStream started producing similar result as soon as I put get_url_params in the IssueStream class, how is this behaviour defined?

oh I understood, silly mistake

had to include pagination tokens as well, works now!