7pace Time Log Migration

Note:

The 7pace add-on is available as an optional paid add-on. Contact sales@migrayt.ai to enable it for your account.

What Gets Migrated

7pace Timetracker stores time log entries against ADO work items. Migrayt migrates each time log entry as a Jira worklog on the corresponding migrated issue.

Each worklog preserves:

Time spent (seconds)
Date and time of the work
Original comment/note from the 7pace entry
Original author attribution (in the worklog comment)

Author Handling

Jira worklogs are written under the migration service account because the 7pace API returns user data by ADO user ID. Where Migrayt can match the ADO user's email to a Jira account, the worklog is created correctly attributed.

For users with no Jira account (ex-employees), the worklog is created under the migration service account with the original author identified in the comment body:

[7pace — Alice Smith on 2024-03-15]

Worked on authentication flow refactor.

Configuration

The 7pace add-on requires API credentials from your 7pace instance. These are provided by your Migrayt account manager and stored securely in Secrets Manager.

Configuration	Description
`pace_api_url`	Your 7pace API base URL (e.g. `https://yourorg.timehub.7pace.com/api/rest/timetracking/v3.2`)
`pace_token`	Bearer token from 7pace Settings → API Tokens
`date_from`	Optional: only migrate time logs after this date (ISO 8601)
`date_to`	Optional: only migrate time logs before this date (ISO 8601)

Minimum Time Log Duration

Time log entries under 60 seconds are skipped to avoid creating noise in Jira from accidental timer starts. There is no maximum duration.

Rate Limits

7pace enforces API rate limits. Migrayt batches requests (200 work item IDs per call) and respects response headers. For very large projects (80,000+ items), the time log fetch phase may take 15–30 minutes.

What Requires Jira Tempo Timesheets?

Migrayt writes worklogs using Jira's native worklog API (POST /rest/api/3/issue/{key}/worklog), which is available on all Jira Cloud plans. You do not need Tempo Timesheets to receive the time data.

If your organisation uses Tempo Timesheets on top of Jira, the native worklogs created by Migrayt are visible in Tempo as well.

Post-Migration Report

The post-migration report includes a 7pace section:

7pace Time Log Migration
───────────────────────────────
Total entries fetched:    8,432
Written to Jira:          8,401
Skipped (< 60s):             14
Failed:                      17
Missing user accounts:       43 emails

Failed entries are listed with the ADO work item ID and error details so you can manually add them in Jira if needed.

Large Projects Xray Test Cases