A command-line microservice that automatically synchronizes Linear issues with your Motion calendar, eliminating the manual effort of keeping your work items in sync between platforms.

The Linear-Motion Sync Tool is designed for developers who use Linear for team project management and Motion for personal task and calendar management. It provides a robust, configurable pipeline to sync assigned Linear issues to your Motion calendar, ensuring your personal to-do list accurately reflects your work commitments.

• Automated Task Creation: Automatically creates Motion tasks from assigned Linear issues
• Bidirectional Status Updates: Marks Linear issues with completion tags when tasks are finished in Motion
• Flexible Configuration: Support for multiple Linear workspaces, custom time estimates, and sync schedules
• Fault Tolerance: Resilient to API failures with comprehensive error logging
• Real-time Updates: Webhook and polling support for immediate synchronization

cargo install linear-motion

ubi --project arlyon/linear-motion

mise use -g cargo:linear-motion

mise use -g ubi:arlyon/linear-motion

Download the latest binary from the GitHub releases page.

1. Initialize configuration:

   linear-motion init

2. Edit the generated config.json with your API keys and preferences

3. Run a one-time sync:

   linear-motion sync

4. Start continuous background syncing:

   linear-motion sync --watch

5. Check sync status:

   linear-motion status

6. (coming soon) Podman Quadlet: Run the daemon under podman + systemd with auto-updates.

To run the sync command periodically as a specific user on a modern Fedora system, the best practice is to create a systemd user service and a corresponding timer unit. This is the modern replacement for user-level cron jobs.

This process involves creating two files in your user's configuration directory.

This file tells systemd what command to run.

1. First, ensure the target directory exists:

   mkdir -p ~/.config/systemd/user/

2. Create the service file:

   nano ~/.config/systemd/user/linear-motion-sync.service

3. Add the following content:

   [Unit]
   Description=Sync Linear Motion data
   
   [Service]
   Type=oneshot
   ExecStart=/linear-motion sync

   • Description: A human-readable description of what the service does
   • Type=oneshot: Suitable for a script that starts, performs a single task, and then exits
   • ExecStart: The full, absolute path to the command you want to run

This file tells systemd when to run the service defined above.

1. Create the timer file (must have the same name as the service file, but with a .timer extension):

   nano ~/.config/systemd/user/linear-motion-sync.timer

2. Add the following content:

   [Unit]
   Description=Run Linear Motion sync once an hour
   
   [Timer]
   OnCalendar=hourly
   Persistent=true
   
   [Install]
   WantedBy=timers.target

   • >: Runs the job at the top of every hour (e.g., 1:00, 2:00, 3:00)
   • Persistent=true: If the system was powered off when the job was supposed to run, it will run as soon as possible after the next boot/login
   • WantedBy=timers.target: Tells systemd how to enable the timer so it starts automatically when you log in

# Reload the systemd user daemon to pick up the new files
systemctl --user daemon-reload

# Enable and start the timer
systemctl --user enable --now linear-motion-sync.timer

{
  "motion_api_key": "your_motion_api_key",
  "sync_sources": [
    {
      "name": "My Team",
      "linear_api_key": "your_linear_api_key",
      "projects": ["PROJECT-1", "PROJECT-2"],
      "webhook_base_url": "https://your-domain.com/webhooks",
      "sync_rules": {
        "default_task_duration_mins": 60,
        "completed_linear_tag": "motioned",
        "time_estimate_strategy": {
          "fibonacci": {
            "1": 30,
            "2": 60,
            "3": 120,
            "5": 240,
            "8": 480
          },
          "default_duration_mins": 60
        }
      }
    }
  ],
  "global_sync_rules": {
    "default_task_duration_mins": 60,
    "completed_linear_tag": "motioned",
    "time_estimate_strategy": {
      "default_duration_mins": 60
    }
  },
  "polling_interval_seconds": 300,
  "schedule_overrides": [
    {
      "name": "Work Hours",
      "interval_seconds": 60,
      "start_time": "09:00",
      "end_time": "17:00",
      "days": ["mon", "tue", "wed", "thu", "fri"]
    }
  ]
}