Guidance on time tracking across two Jira instances (TimeCamp)

[James Hamm]

We use Jira Cloud with TimeCamp to track time per issue. For a current engagement, the issues live in our partner agency’s separate Jira Cloud instance. TimeCamp appears to allow only one Jira integration per workspace, so our team can’t start timers tied directly to the agency’s issues.

Could you recommend an Atlassian-approved approach to keep per-issue time tracking while the source of truth remains in the agency’s Jira?

We’re considering:

• Jira↔Jira mirroring/sync into a project in our instance (so our team tracks time on the mirrored issues that TimeCamp can see). If this is the best practice, which Marketplace apps do you recommend, and do they require installation on both instances? Any gotchas around fields, comments, attachments, or status mapping?

• Atlassian Automation or other native options for cross-instance issue creation/updates (lightweight “stubs” in our instance) — is this feasible/recommended?

• Alternative time-tracking add-ons (e.g., Tempo, etc.) that might better handle cross-instance scenarios.

Constraints/requirements:

• Keep the agency’s project as the single source of truth.

• Minimize overhead for engineers (start/stop timers from issues they’re already working in).

• Clean reporting on our side (ideally keeping a reference to the original issue key).

If you can point us to recommended apps, docs, or a configuration pattern — or set up a quick call — that would be great.