Sync tasks with Jira, ClickUp or GitHub

Task sync keeps work items in a Cyborg project in step with issues or tasks in another tool. You connect the tool once for the workspace, then link a project: pick which Jira project, ClickUp List or GitHub repository fills which Cyborg project.

The import wizard and live sync view below apply to Jira and ClickUp. GitHub links a repository instead. See GitHub.

Connect the tool

1. Open Settings → Integrations and click Jira, ClickUp or GitHub, then Connect (Manage once connected).
2. Approve access in the tool’s window. Jira and ClickUp list the connected site or workspace under Connected site / Connected workspace. A row that says Reconnect needed needs its Reconnect button.

Step-by-step connect guides: Jira, ClickUp, GitHub.

Link a project (Jira and ClickUp)

On the tool’s page, Link a project opens a wizard. When a project is already linked the section reads Link another project with a Link project button. The steps are shown at the top of the wizard.

1. Project (or List)

Choose what to follow.

• If you have more than one connection, first choose the Site (Jira) or Workspace (ClickUp).
• “Which Jira project should this workspace follow?” (for ClickUp, “Which ClickUp list…”). Each choice shows how many open issues and people it has. “Pick one now. You can link more later.”
• Fill this Cyborg project: the Cyborg project that receives the work items.
• If the connection can’t list projects, type an id instead: cloudId:KEY for Jira, or a List id such as 901234 for ClickUp.

2. Tasks

“Which tasks come over?” Counts are read from the tool just now, and each bucket has a switch:

• Backlog
• To do
• In progress
• Done, last 7 days

Old finished work stays where it is. The Total row shows how many tasks will import (titles, descriptions, status, priority, people, labels, dates, sub-tasks, comments and attachments).

Under Status matching, each status from the tool is matched to a Cyborg workflow state. Statuses that don’t match by name are listed, with Not matched yet for any that have no match. Click Change status matching to see every status and pick the Cyborg state for each (or Not matched).

3. People

“Who is who?” Cyborg looks for your teammates by email (“Matching by email”). Everyone it finds shows a check and by email. For the rest, choose a Cyborg person, or Leave unassigned. Anyone you skip imports as unassigned. If someone is not in Cyborg yet, use Invite them. If the tool hides an email, the row says email hidden by <tool>.

4. Review

Ready to bring N tasks into <project>. Choose how the two sides behave after the import:

• Two-way sync: a task made here appears in Jira (or ClickUp), and the other way round. Every edit follows.
• Only from Jira (or Only from ClickUp): the tool stays the source. Nothing is written back.

Click Import N tasks. Progress shows: Tasks, status and people, Labels and priorities, Comments and sub-tasks, Attachments, then Turn on live sync. When it finishes, Go to board opens the project’s tasks.

The live sync view

Once a project is linked, a Live sync section appears on the tool’s page. With more than one linked project, choose one under Linked project. It shows:

• A status pill: In sync · both ways (or In sync · following Jira), Syncing… while a change is moving, Reconnect needed, or Some changes did not sync. A diagram shows Cyborg and the tool, with how many tasks each side has.
• Last change from Jira, Last change sent to Jira (shows Off for an only-from sync), and Linked tasks.
• Live activity: a feed of what changed on either side, for example “Marta moved PLAT-402 to In Review”. Each line says whether it came from or went to the tool. Show older loads earlier entries. Until something changes it reads “Changes on either side show up here.”

When something fails

A banner says how many changes could not reach Cyborg or the tool, and why, for example: 1 change could not reach Jira: PLAT-431: <reason>. It offers:

• Reconnect (shown when the connection needs signing in again),
• Fix it, which retries after you have corrected the cause, and
• Dismiss, which clears the entry.

GitHub

GitHub does not use this wizard. Install the GitHub App, then use Link repository to sync a repository’s issues with a Cyborg project and map pull request states to workflow states. See GitHub.