Migrate from YouTrack to Jira

YouTrack Issues map to Jira Issues as the primary migration unit. Standard fields (summary, description, status, priority, type, created, updated) migrate directly. YouTrack's $type and $workflow fields map to Jira's Issuetype and Status respectively. Description content migrates as Jira's Description field, with Markdown converted to Jira's wiki-style markup. Parent-child issue links migrate as Jira Issue Links (blocks, is blocked by, relates to, subtask) using the parent-issue resolution step.

YouTrack Projects map to Jira Projects. Project type (Scrum, Kanban, Bug-tracking) is preserved as a custom property to maintain workflow context. We recreate YouTrack project configurations in Jira including project lead, default assignee, and notification scheme. Jira Projects require a Project Type and a Lead at creation time, so we resolve these from YouTrack's projectOwner and defaultAssignee fields during the project-creation phase before any Issue migration begins.

YouTrack's CustomField defines a field globally while ProjectCustomField controls per-project visibility and defaults. We export the global field definition plus all project bindings and default values, then create Jira Custom Fields of the equivalent type (text, number, date, picker, multi-picker) with Jira field contexts scoped to the relevant projects and issue types. Field references in YouTrack's ProjectCustomField instances are resolved to Jira's customfield_xxxxx API names during field creation.

YouTrack Agile Boards store configuration including swimlanes, column definitions, and sprint associations. We export board definitions and re-create them in Jira with the appropriate Board Type (Scrum or Kanban). Jira boards require a configured backlog and sprint configuration for Scrum boards; we extract sprint definitions from YouTrack's sprints entity and recreate them as Jira Sprints before board association. Swimlane configuration migrates as Jira swimlane settings.

YouTrack Attachments are stored as PersistentFile entities linked to Issues. We download file content via the YouTrack REST API, preserving original filenames and MIME types, then upload to Jira Issues via the Jira REST API's multipart attachment endpoint. Large attachments exceeding Jira's 32 MB per-file limit are flagged and escalated to the customer's admin for manual handling.

YouTrack Tags are label entities attached to Issues. We preserve the full tag set per Issue and recreate them in Jira as Labels. Labels in Jira are plain text tags without the rich metadata that YouTrack stores on tag entities, so any tag descriptions or custom tag properties beyond the name are documented for the customer's admin to handle as a Jira label-management convention.

YouTrack ProjectTeam entities define group membership per project. We map group memberships to Jira Project Roles (which are named collections of users or groups) and Jira Permission Schemes. YouTrack's role-based permissions (Viewer, Reporter, Member, Manager, Administrator) map to Jira's permission set model (Browse Projects, Create Issues, Edit Issues, Manage Sprint, Administer Projects) based on a role-mapping matrix agreed during scoping.

YouTrack Workitems store time spent linked to Issues and Users. We export work entries with duration, description, created date, and author, then create Jira Worklogs via the Jira REST API. YouTrack duration in minutes converts to Jira's time tracking format (e.g., 2h 30m). Worklog author is resolved via the User mapping by email match. If YouTrack uses billing fields on Workitems, these migrate to Jira custom fields on the Worklog object.

YouTrack Saved Queries store filter definitions referencing field names, operators, and values using YouTrack's query language. We export these definitions and convert them to Jira Query Language (JQL) equivalents. Field name references are mapped to Jira field IDs during conversion. Saved Filters are shared with the appropriate project roles in Jira. Filters that reference migrated Issue IDs are updated with the new Jira issue key prefix after Issue migration.

YouTrack Comments attach to Issues with author, body, created timestamp, and updated timestamp. We export all comments via the YouTrack REST API and create Jira Comments via the Jira REST API, preserving the author mapping (via email-to-User resolution), body content, and timestamps. Rich-text comments with mentions or images are handled with basic Markdown conversion to Jira's comment format.

YouTrack IssueLinks store typed relationships between Issues (blocks, is blocked by, relates to, parent, subtask, duplicate). We export all link types and create Jira Issue Links with equivalent link types during Issue migration. Because Jira requires the destination Issue to exist before creating links, we run a two-pass approach: create all Issues first without links, then update each Issue with its outgoing links in a second pass once all Issue IDs are known.

YouTrack issue history (field change log) migrates as Jira Issue History. We export change entries up to YouTrack's 1,000-change cap per issue and create Jira Change history entries via the Jira REST API. YouTrack's $timestamp and $author fields map to Jira's created and author fields on each history entry. Changes that reference values that did not migrate (e.g., deleted users or removed custom field options) are logged and flagged in the reconciliation report.