How to Create Labels in Jira: A Step-by-Step Guide for Teams
Want to organize Jira issues more easily? Learn how to create labels in Jira and keep team tags consistent. Click to discover the step-by-step guide.
Labels can make Jira issues easier to group, search, and report on. Yet a new label can quickly create confusion if your team uses different spellings or adds labels without a shared purpose.
That confusion grows as projects accumulate near-duplicates such as customer-feedback, customer_feedback, and feedback. Searches become less reliable, and useful patterns can disappear among inconsistent tags.
But here's the truth: adding a label is simple once you know where to find the Labels field. A few team conventions help keep labels useful after you create them. This guide walks you through adding labels to one issue or many, finding labeled work, removing labels, and preventing common naming problems. You’ll also see when labels are enough and when a team may need more structured project-management practices.
How to create labels in Jira
You can add a label while creating or editing an issue. Jira labels are flexible text tags, so agree on a naming style before your team starts adding them freely.
Open the issue. Go to the Jira project and select the issue you want to tag. You can add a label to an existing issue or enter one while creating a new issue.
Choose Edit. Select the issue’s Edit option. In the edit screen, look for the field named Labels. Jira’s exact layout can vary by version and project configuration.
Enter the label. Type a short, descriptive term, such as accessibility or release-2-4. If Jira displays suggestions, choose an existing label when it matches your intended meaning.
Add more labels if needed. A single issue can have multiple labels. Use them only when each one helps describe or find the work; several overlapping tags can make searches harder to interpret.
Save the issue. Select Update or the equivalent save action. Reopen the issue and check that the label appears in its details.
Confirm the label is searchable. Search for the label using Jira’s issue search. For example, the JQL query labels = "accessibility" finds issues carrying that label.
Can’t see the Labels field? Your issue’s edit screen or project configuration may not include it. Ask a Jira administrator to check the field configuration and screen setup for that issue type.

Choose a naming convention before labels spread
Labels are easy to create because they don’t require a long setup process. That flexibility can produce several labels for the same idea, especially when teammates work independently.
For example, a team might use bug-bash, bugbash, and bug_bash for the same activity. Pick one style, such as lowercase words with hyphens, and share a short list of approved labels.
Here's why: a consistent label is easier to remember and search. Use labels for cross-cutting themes, such as accessibility or customer-feedback, rather than details Jira already tracks in dedicated fields.
Find Jira issues by label
After you add labels, Jira search can help you find related work across issues. In basic search, choose the Labels field and enter the term you want to find.
For a more precise search, use JQL. The query labels = "accessibility" finds issues with that label, while labels in ("accessibility", "mobile") finds issues carrying either label.
You might be wondering: what if you need issues with both labels? Use labels = "accessibility" AND labels = "mobile". Save a useful search as a filter if you expect to revisit it regularly.
Add or remove labels across several issues
When the same label belongs on many issues, bulk editing can save time. Search for the relevant issues first, then select the available bulk change action and choose the option to edit labels.
Jira’s bulk-edit permissions and interface vary by project and edition. Review the selected issues before applying a change. A broad search can accidentally tag unrelated tasks, such as closed work or issues from another team.
To remove a label, edit the issue and delete that term from its Labels field. For a group of issues, use bulk edit when your Jira configuration allows it. Check a few updated issues afterward to confirm the right label was removed.
Keep labels useful as your team grows
Labels work well for lightweight categorization, such as campaign themes, temporary investigations, or cross-team topics. They can become harder to manage when teams use them to represent required stages, owners, or priority levels.
For example, a label like needs-review may help during a short review effort. If every issue must move through a formal approval process, a workflow status or dedicated field may communicate that requirement more clearly.
The best part? You don’t need a long policy. Ask teammates to search for an existing label before creating another, agree on naming rules, and review rarely used labels occasionally.
A broader project-management option: ONES.com
ONES.com is a unified project-management and knowledge-management platform powered by ONES Assistant. ONES Project is its project-management product and a Jira alternative; ONES Wiki is its knowledge-base product and a Confluence alternative. They are sold separately.

If your team’s needs extend beyond adding tags, ONES Project may be worth evaluating alongside your current approach. Its Jira-compatible workflows can support teams that want familiar project structures, while built-in reporting and customization can reduce reliance on extra plugins.
Core capabilities
Too many separate work tools → Jira-compatible workflows → familiar ways to manage project work. Teams can evaluate an alternative without abandoning common workflow patterns.
Reporting requires extra setup → Built-in reporting → project progress is easier to review in the platform. Teams can use reporting capabilities without relying on a separate reporting plugin for every need.
Fixed processes don’t fit every team → Custom workflows → work can follow team-specific steps. A team can shape how work moves instead of forcing every project into one process.
Standard fields leave gaps → Custom fields → teams can capture details relevant to their work. This can help when a project needs structured information beyond basic issue details.
Sprint work needs coordination → Sprint management → teams can organize and track planned work. This supports teams using iterative delivery practices.
Repeated manual actions take time → Automation → routine project actions can run with less manual effort. Teams can reserve more attention for work that needs judgment.
Plugin dependence adds complexity → Native feature parity between cloud and self-hosted versions → teams can assess deployment choices while retaining feature access. This can help organizations that prefer fewer add-ons.
Strict hosting requirements limit choices → Cloud, On-Premise, Private Cloud, and Air-gapped deployments → organizations can evaluate an option that fits their environment. ONES.com also offers a free plan for up to 30 seats.
Application scenarios
A growing product team might compare ONES Project with Jira when its current setup relies on several plugins for reporting, workflow changes, and sprint coordination. The team can assess whether built-in capabilities fit its day-to-day process.
An organization with restricted network requirements may evaluate the On-Premise, Private Cloud, or Air-gapped deployment options. If the same organization also needs a knowledge base, it can assess ONES Wiki separately from ONES Project.
Common challenges with Jira labels
Problem: You can’t find the Labels field. Solution: Check whether the field appears on the issue’s create or edit screen. If it does not, ask a Jira administrator to review the project’s field and screen configuration.
Problem: Similar labels split search results. Solution: Agree on a standard spelling and naming format. When appropriate, update issues to use the preferred label and remove obsolete variations.
Problem: Search results include unexpected issues. Solution: Review the JQL query, project scope, and label spelling. Add conditions such as project or status when you need a narrower set of issues.
Problem: A bulk change affects the wrong issues. Solution: Inspect the search results before applying the change. Start with a small group and verify the outcome before repeating the action more broadly.
FAQs
Can I create a Jira label before assigning it to an issue?
In typical Jira use, a label becomes available when someone adds it to an issue. There usually isn’t a separate label-creation step needed first. Type the label in the Labels field while creating or editing an issue, then save the issue. Your Jira configuration may affect how the field appears and which suggestions are shown.
Can one Jira issue have more than one label?
Yes. You can add multiple labels to an issue when each one describes a useful aspect of the work. For example, a mobile accessibility task might use both mobile and accessibility. Keep the number purposeful so teammates can understand what each label means and use it consistently.
Why can’t I add a label to an issue?
The Labels field may be missing from the screen, or your account may not have permission to edit that issue. Check whether you can edit other issue details. If the field itself is absent, ask a Jira administrator to review the project configuration and the screen associated with the issue type.
What is the difference between a Jira label and a component?
Labels are flexible tags that teams can add to issues for informal grouping or search. Components are project-level categories that may have assigned owners and other project-specific settings. Use a label for a cross-cutting theme such as accessibility; consider a component when the category represents a defined part of the project.
Conclusion
Adding a Jira label takes only a few steps: open an issue, edit its Labels field, enter a clear term, and save. You can then find matching work through basic search or JQL, and use bulk edit when the same change applies across several issues.
Labels are most useful when teammates follow a shared naming style and check for existing terms before adding new ones. Start with a small, practical set, then adjust it as your work changes. If managing projects requires more structured workflows or reporting, compare your current setup with broader options such as ONES Project.