The short answer
Components are a fixed list of parts of the work, such as Mobile app, Payments API or Website, set up by a space admin. They exist only in company-managed spaces, and each component can have an owner who is auto-assigned work.
Labels are free-form tags anyone can type, such as receipts or q3-audit. They need no setup and can be shared across company-managed spaces.
Use components for the stable structure your team agreed on. Use labels for everything ad hoc: a campaign, a theme, a one-off clean-up.
Side by side
| Components | Labels | |
|---|---|---|
| Who creates them | Space admins | Anyone, by typing |
| Where they work | Company-managed spaces only | Shared across company-managed spaces |
| Auto-assign | Yes, via owners | No |
| Spaces in the name | Allowed | Not allowed |
Components in detail
Atlassian describes components as a way to group work items in your space around product features, departments or workstreams. A few properties matter:
- Company-managed only. Atlassian's help says Jira components are only available in company-managed spaces and are scoped to the space they are created in. In a team-managed space, you will not find the field.
- Set up by admins. Space admins configure them. Everyone else in the space can view and search for components and link work items to them.
- Owners and auto-assignment. You can assign component owners and have people auto-assigned to work items linked to those components. Pick the "Payments API" component and the ticket can land with that team's owner without anyone choosing an assignee.
Because the list is fixed, components stay tidy: nobody creates "Payment API" next to "Payments API" by accident.
Some spaces use Compass components instead of Jira components, for grouping work around pieces of software. Atlassian notes a space cannot use both at the same time.
Labels in detail
To add a label, open the ticket, find the Labels field, start typing, and press Enter or pick one from the suggestions. Some details from Atlassian's help:
- No spaces. Labels cannot contain spaces, so use hyphens or underscores:
month-end,q3_audit. - Suggestions help you stay consistent. Jira suggests existing labels as you type. Pick the suggestion rather than typing your own spelling.
- Shared between spaces. Labels created in one company-managed space are visible in other company-managed spaces, as long as the Labels field is enabled there.
- A short delay. A newly created label can take up to 15 to 20 minutes to appear for other people.
- Labels vanish when unused. If a label is on only one work item and you remove it, the label is deleted.
The freedom is also the risk: receipts, receipt and Receipts-redesign can all end up on the same board, and a search for one misses the others.
When to use which
- "Which part of the product is this?" Component, if your space has them.
- "Who should get this by default?" Component with an owner.
- "Which initiative, campaign or theme does this belong to?" Label, unless it is big enough to be an epic (see what an epic is).
- "I need to find these 12 tickets again next week." Label.
Labels, components and epics can overlap. An epic is a piece of work with an end; a component is a lasting part of the product; a label is a tag for whatever cuts across them.
Follow your team's rules first
Whatever this guide says, your team's habits win. Before you add a component or a label:
- Look at a few tickets on your board and see what they use.
- Reuse existing labels from the suggestions instead of inventing new ones.
- If a board seems to filter on a component or label, add it, or your ticket may not show up on that board (see ticket not showing on the board).
Practise reading ticket fields
Knowing what each field on a ticket tells you is the first step. Agile Board Practice has a lesson where you read a ticket's key, summary, status, people, priority, description and comments on a practice board, with feedback on each step.
Frequently asked questions
What is the difference between components and labels in Jira?
Components are a fixed list set up by space admins, only in company-managed spaces, and can auto-assign work to an owner. Labels are free-form tags anyone can type and can be shared across company-managed spaces.
Can I use components in a team-managed space?
No. Atlassian's help says Jira components are only available in company-managed spaces.
Why can't I add a label with a space in it?
Labels cannot contain spaces. Use hyphens or underscores instead, such as month-end.
Who can create components in Jira?
Space admins configure components. Everyone else in the space can view them, search for them and link work items to them.
Why doesn't my new label show up for others?
Atlassian notes a newly created label can take up to 15 to 20 minutes to appear for other people, who may also need to refresh.