Repository navigation
jira integration part 3 - show diff between tmetric and jira - #33
Conversation
121b1ec to
a32f674
Compare
There was a problem hiding this comment.
🟡 Changes recommended
The Jira integration breaks OpenProject-only configurations and can fail or produce incorrect totals due to timezone boundaries, oversized worklog requests, and missing author filtering.
4 open issues
What changed in this PR
Builds on the Jira copy integration by extending diff to compare Tmetric entries with Jira worklogs alongside OpenProject time entries.
Changes:
- Fetches Jira worklogs and displays issue details, durations, and combined time differences.
- Adds user timezone metadata and timezone-aware Jira worklog conversion.
- Updates client-scoped validation, copy commands, setup documentation, and the HTTP dependency.
| File | Description |
|---|---|
tmetric/user.go |
Captures timezone metadata from both user API formats. |
tmetric/tmetric.go |
Adds client filters to entry validation and transfer selection. |
tmetric/tmetric_test.go |
Updates validation tests and adds client-filter cases. |
tmetric/timeentry.go |
Converts entries to Jira worklogs using user timezones. |
README.md |
Documents timezone setup and destination-specific copy commands. |
jira/worklog.go |
Adds worklog models, metadata handling, comment extraction, and saving. |
jira/jira.go |
Retrieves worklogs and filters them for comparison. |
jira/issue.go |
Adds project details to Jira issue data. |
go.sum |
Adds checksums for the updated Resty dependency. |
go.mod |
Updates Resty to version 2.17.2. |
config/config.go |
Removes the obsolete client field while retaining configuration validation. |
cmd/tmetric.go |
Adapts checks to the client-filter parameters. |
cmd/diff.go |
Includes Jira entries in the comparison table and totals. |
cmd/copy.go |
Shares validation and selection between destination subcommands. |
cmd/copy-openproject.go |
Separates OpenProject copying into its own subcommand. |
cmd/copy-jira.go |
Adds the Jira copy subcommand and transfer flow. |
Review effort: Balanced
a32f674 to
4b1c3bd
Compare
4b1c3bd to
f59f1ae
Compare
…successful lookups' Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
…ep warnings aligned' Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
|
The diff for jira didn't show up for few seconds. This is what I did.
Result: On running the diff command for first time the time log of jira was not listed under I followed these step 2-3 times and 2 out of 3 times I saw this behavior. If we wait for few seconds before running the diff command then we get the correct diff. |
|
I saw that behavior also in other places, e.g. when changing values in the UI it takes awhile till they are available through the API. I guess that is the nature of the DB / backend Jira is using. |

With this change the
diffcommand will also include: