jira_issue_worklogs: use updated to get worklogs

[mariusgrigaitis]

Example query results

Results

> select count(*) from jira_issue_worklog
+-------+
| count |
+-------+
| 1913  |
+-------+

Time: 15.7s. Rows returned: 0. Rows fetched: 1,913. Hydrate calls: 0.

> select count(*) from jira_issue_worklog where issue_id = '2261424';
+-------+
| count |
+-------+
| 1     |
+-------+

Time: 397ms. Rows returned: 0. Rows fetched: 1. Hydrate calls: 0.

> select count(*) from jira_issue_worklog where updated > '2025-01-01 00:00:00'::timestamptz;
+-------+
| count |
+-------+
| 313   |
+-------+

Time: 3.6s. Rows returned: 0. Rows fetched: 313. Hydrate calls: 0.

This PR improves the worklog retrieval functionality by filtering on the updated field, leading to more efficient queries such as:

select count(*) from jira_issue_worklog where updated > '2025-01-01 00:00:00'::timestamptz

Key changes include:

• Efficient querying based on the updated field.
• Removal of the ParentHydrate dependency from jira_issue_worklog.
• Note: When an issue_id is not provided, the default filter (updated > 0) allows fetching all worklog entries.

This update may also make issue #148 redundant.

[ParthaI]

Thanks for raising the PR! It would be helpful to include observations in the PR body, such as query execution time, the number of API calls made, and results from different query parameter combinations.

Additionally, we haven't explicitly handled the </<= operators for the updated value in the WHERE clause. I'm curious to see how the table behaves in such scenarios. Looking forward to your insights! 🚀

[mariusgrigaitis]

Sample queries are actually in PR description (under collapsed section)

<=/< should still work by getting all records

[ParthaI]

Hello @mingfang, I have left a few review comments. Please have a look when you get a chance, Thanks!

[ParthaI]

LGTM