Understand a Unit and its sync behavior

A Unit is the main place where work, context, collaboration, Orbit, and Lenses come together.

Unit header

The header can show the title, status, assignee or owner, date, participants, priority, and additional controls. Work Units also show their source identifier, such as a Jira issue key.

Description and tabs

The description explains the Unit. Tabs can include Attachments, Relationships, and Activity. Available Unit tools can include time tracking, Estimations, Documents, and Diagrams.

What can sync

For supported Work Units, status and assignee can sync where the provider exposes them. Estimate, time, comments, attachments, and relationships differ by provider and feature.

Current examples:

• Jira and Azure DevOps support sprint, status, and type sync rules.
• Linear supports cycle and status rules.
• monday.com supports group and status rules.
• GitHub Issues, Trello, Todoist, and Wrike currently use hand-pick import.
• Provider comments can contribute Lens signals for Jira, Azure DevOps, Linear, monday.com, and Wrike.

Documents, Diagrams, and Quely Threads remain in Quely. Do not assume a Quely Thread becomes a provider comment.

Context Units

A Context Unit is native to Quely and does not have an external task identifier. It can reference several connected sources but belongs to one Space.

If information looks wrong

• Confirm whether the Unit is Work or Context.
• Confirm the source connection is active.
• Check the source tool for the current field value.
• Refresh or wait for the supported synchronization process.
• Contact support if changes remain inconsistent.

Next steps

Next: Discuss work in Threads

Related articles:

• Work Units and Context Units
• How Quely connects to your tools

Updated on: 14/08/2026