Skip to main content
Use Project settings → Work → Import from Linear to bring an existing Linear project into a managed ReasonOS project’s Work issues. A Linear project is the import unit: issues from all of its visible teams are included. This does not import a whole Linear workspace or turn on continuous synchronization.

​
Connect and preview

Before you connect, an operator must configure a Linear OAuth application for the ReasonOS deployment. Until that is ready, an operator can use the temporary personal API-key connection when the operator-only fallback is enabled. Customers are not expected to paste their own keys.
  1. Open the destination ReasonOS project and go to Settings → Work → Import from Linear. You need permission to manage that project’s settings.
  2. If OAuth is configured, select Connect Linear and authorize read access in Linear. Otherwise, ask your operator about the temporary API-key connection. The connection belongs to this ReasonOS project; its credential is held by the control plane, not shown in the browser.
  3. Choose a Linear project. Review the preview’s issue, comment, label, archived, and already-imported counts; status mapping; and matched and unmatched people. Decide whether to include archived issues and comments. These counts come from the preview, not the Linear project list.
  4. Select Start import. This accepts a background job; it does not mean the import has finished. Watch its phase and counts in Import history.
The import maps Linear status categories to existing ReasonOS Work statuses. Check the preview before starting; it does not create new statuses named after Linear’s workflow. Unmatched people remain attributed by their Linear name rather than being turned into ReasonOS members.

​
What appears in Work

Imported issues retain their Linear identifier and a link to the source issue. Historical comments display their original author via Linear, even when that person’s email matches a ReasonOS member. The import does not post mentions, wake agents, or send comment notifications on their behalf. The initial import includes the Linear project’s issues, status category, priority, labels, due date, hierarchy, comments (if selected), and source links. A project-level initiative provides a place to group the imported issues. Linear cycles and issue relations are not imported in this version. For an issue with more than 100 comments, the first 100 are imported and the remaining comments are reported as skipped. ReasonOS creation and author timestamps are not rewritten to look as if the records were created here in the past; the original Linear timestamps remain in source provenance.

​
Reruns and failures

The import is add-only. Starting it again skips source records already imported and can fill in missing records from a partial run; it does not overwrite edits made in ReasonOS or delete issues that disappeared from Linear. It is a migration path, not a two-way sync. An import can finish with individual failures. Read the created, skipped, and failed counts, then open Failed items to see the source identifier and reason. Resolve the cause and rerun if needed. If Linear’s API budget is exhausted, the progress note may show that the job is waiting before it can continue. Do not infer completion from a request that merely accepted the job. Disconnecting Linear removes the connection, not imported Work issues. The source identifier and links remain on those issues.
This feature is for managed ReasonOS projects. A local branch node or editor session does not run the import. If you are migrating a customer project into production, confirm the destination project and Linear access with your ReasonOS operator before starting.