Migrate from TimeHero to Jira

TimeHero tasks map to Jira issues with Jira issuetype set to Story for customer-facing or deliverable work and Task for internal work. TimeHero title maps to Jira Summary; TimeHero work estimate maps to Jira Original Estimate (custom field or Time Tracking); TimeHero actual duration maps to Jira Time Spent via worklog; TimeHero remaining time maps to a custom Remaining Estimate field. Both the original due date and the current TimeHero scheduled date are preserved as separate Jira custom fields so that scheduling context is not lost during migration.

TimeHero projects and folders export as Jira Projects. We create a Jira Project per TimeHero project or folder, preserving the project name and using it as the Jira Project Key prefix (e.g., TH-PROJ becomes a Jira project with key THPROJ). The project configuration (issue types available, default workflow, field configuration) is designed during the pre-migration Jira configuration phase before data ingestion begins.

TimeHero's actual duration and remaining time embedded in task records map to Jira Worklog entries on the corresponding Jira issue. Each worklog records the duration, the date the work occurred (from the TimeHero completion or activity date), and the author (resolved via user email match against Jira users). Time tracking must be enabled on the Jira project before migration ingestion begins.

TimeHero recurring task patterns (daily, weekly, monthly, custom interval) are extracted and documented during migration scoping. Jira has no native recurring issue feature, so we deliver a written rule book listing each recurring task's recurrence pattern (frequency, interval, start date, end condition) with the equivalent Jira Automation trigger configuration. The customer's Jira admin implements the automation rules post-migration.

TimeHero assignee information maps to Jira User records via email address lookup. Any assignee with no matching Jira user is flagged in a reconciliation queue before migration ingestion. The customer provisions missing Jira users (active or inactive matching the TimeHero user status) before the main migration phase begins.

TimeHero priority levels (Critical, High, Medium, Low or numbered) map directly to Jira Priority values. Jira's default priority scheme (Highest, High, Medium, Low, Lowest) accommodates the TimeHero range. We create a priority mapping table during scoping and apply it as the Jira Priority field during issue ingestion.

TimeHero uses Google and Outlook calendar events as scheduling context rather than storing them as primary records. If the customer wants historical meeting commitments preserved as Jira issues (e.g., sprint planning sessions, stakeholder reviews), we can optionally import them as Jira issues with issuetype = Task and a label indicating calendar-origin. This is an opt-in scope item confirmed during discovery.

TimeHero risk flags (tasks at risk due to deadline proximity or scheduling conflict) are computed values not stored fields. We extract the triggering conditions — deadline date, assigned capacity, conflict timestamp — and surface them as Jira labels (risk/ deadline-at-risk, risk/ capacity-overload) or as linked Jira issues (Blocks relationship) to the at-risk task. This preserves risk awareness without a direct equivalent field.

TimeHero workload reports showing team capacity and task distribution are derived from underlying task data. We extract all assigned tasks, their due dates, and assignees, then create Jira issues under the appropriate project. Once ingested, Jira's native board views and sprint burndown charts reproduce the workload overview that TimeHero provided.

TimeHero's Asana connector syncs assigned tasks from Asana into the TimeHero inbox for scheduling. Any Asana-assigned tasks that were synced into TimeHero and now need to land in Jira are identified by their integration-source label during scoping. We migrate these as Jira issues using the same assignee and scheduling context that was stored in TimeHero, flagging them with an integration-source label for traceability.