> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.quely.io/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Work Units and Context Units


Every Unit is either Work or Context. Group is an organizing container.

## Work: What needs to get done?

A Work Unit is linked to an external issue, ticket, or task. Current Work providers are Jira, Azure DevOps, GitHub Issues, Linear, monday.com, Trello, Todoist, and Wrike.

Provider capabilities differ. All eight support hand-picking. Some also support live rules by sprint-like group, status, or type.

## Context: What should we understand?

A Context Unit is native to Quely and creates a living understanding of a subject. In the current builder, **Custom** is available. Customer, Feature, Initiative, Release, Team, Theme, Competitor, and Product area are marked **Soon**.

The current Context source is Confluence.

## Group: How is it organized?

A Group organizes related Units inside one Space. It is not a third Unit type.


![Work Units and Context Units](https://storage.crisp.chat/users/helpdesk/website/-/a/8/4/2/a842a666ac554800/what-are-you-adding_k8jww6.png)
## Choose Work when

* The item already exists in a supported work provider
* Source fields should stay connected where supported
* The team is acting on defined work

## Choose Context when

* The subject spans several items
* Confluence contains the source material
* The team needs a focused understanding rather than another task

---

## Next steps

**Next:** Add Work Units from a connected tool

**Related articles:**

* Create a Context Unit