How to Create a Label in Jira: Steps and Best Practices
Searching for “jira create label”? Learn the steps and best practices to keep issue tags organized. Read now to get started.
Jira labels help you group related issues, but an inconsistent naming habit can quickly make them hard to use. One teammate adds website, another adds Website, and a useful filter starts missing work.
That clutter makes sprint reviews, bug triage, and project searches more frustrating than they need to be. The good news is that adding a label takes only a few clicks, and a simple naming convention keeps the system tidy.
Here’s how to create a label in Jira, apply it to issues, find labeled work, and prevent common mistakes. I’ll also explain when labels are useful and when a structured field or workflow may serve your team better.
How to Create and Apply a Label in Jira
To create a label in Jira, open an issue, edit its Labels field, enter the label, and save the issue. Jira adds a new label when you enter a value that does not already exist.
Open the Jira issue you want to categorize. You can create a label while editing an existing issue or creating a new one.
Select Edit, or locate the Labels field directly on the issue screen if your Jira layout allows inline editing.
Click the Labels field and type a short, descriptive term, such as accessibility or release-2025-04.
Press Enter to confirm the value. If Jira displays matching labels, choose the existing label when it fits your purpose.
Add any other needed labels, then save or update the issue. The label is now attached to that issue and available for other issues.
Open another issue and repeat the process to apply the same label. Labels are reusable, so you do not need to create a separate one for each issue.
But here's the truth: a label may not appear in a central list until someone has used it. If you cannot find the Labels field, check whether your project’s issue layout includes it or ask a Jira administrator about your permissions.

When Jira Labels Are Useful
Labels work well for flexible tags that cut across project components, teams, or issue types. For example, a product team might tag issues with accessibility to find work related to keyboard navigation and screen-reader support.
They can also group work that matters only for a short period. A team preparing for a launch might use launch-checklist to find related bugs and tasks without changing each issue’s project or component.
Here's why: labels are quick to add and can be reused across issues. They are especially handy when a category is useful but does not need its own dedicated field or formal workflow.
Labels are less suitable when a value must be consistent, mandatory, or restricted to a controlled set. If every issue needs a defined customer tier, for instance, a custom field is usually easier to govern than free-form labels.
Find and Manage Issues by Label
After applying labels, you can search for related issues in Jira. In basic search, choose the Labels field and enter the term you want to find.
For more control, use Jira Query Language (JQL). A query such as labels = accessibility finds issues carrying that label. You can add conditions to narrow the results, such as project = APP AND labels = accessibility.
The best part? A saved filter can make a recurring search easier to reuse. For example, save a filter for accessibility issues, then share it with teammates who review that work.
Labels can also be changed or removed by editing the issue. If an old tag no longer fits, remove it from affected issues and agree on a replacement before introducing another variation.
Labeling Practices That Keep Jira Searchable
Use a short naming convention before labels spread across projects. A team might choose lowercase words joined with hyphens, such as customer-feedback, and ask everyone to follow that pattern.
Before adding a new label, search Jira for similar terms. If performance already captures the intended work, adding perf may split results across two labels.
Use labels for cross-cutting, informal categories. Keep more permanent classifications, such as issue ownership or release status, in fields designed for consistent reporting and workflow rules.
Review labels occasionally, especially after a project or release ends. A short cleanup can reveal duplicates, outdated tags, and categories that deserve a more structured field.
ONES.com Solution for Coordinating Project Work

Value Proposition
When Jira labels are part of a larger coordination problem, ONES.com offers a unified platform for project management and knowledge management. ONES Project is its project management product and a Jira alternative; ONES Wiki is its knowledge management product and a Confluence alternative. They are sold separately.
This distinction matters: a team can choose project management, knowledge management, or both without treating labels as a substitute for a full work process. ONES.com supports Cloud, On-Premise, Private Cloud, and Air-gapped deployments, with feature parity between cloud and self-hosted versions.
Core Capabilities
Work is scattered across disconnected tools → ONES.com brings project and knowledge management together on one platform, while ONES Project and ONES Wiki remain separately available → teams can select the products that fit their needs.
Teams rely on Jira-specific processes → ONES Project supports Jira-compatible workflows → teams can carry familiar workflow patterns into a Jira alternative.
Labels alone do not capture required issue details → ONES Project supports custom fields → teams can record consistent information in defined fields.
Work moves through inconsistent steps → Custom workflows let teams shape how issues progress → each group can align issue handling with its process.
Sprint planning needs clearer coordination → Sprint management supports iterative project work → teams can organize work around planned cycles.
Teams need visibility into progress → Built-in reporting provides project insights → leads can review work without relying only on individual issue searches.
Repeated actions consume time → Automation can handle supported recurring project tasks → teams can reduce routine manual steps.
Plugin dependence adds operational overhead → Native capabilities cover workflows, fields, reporting, sprint management, and automation → teams may be able to reduce the number of separate plugins they rely on.
Deployment requirements vary → ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped options, with a free plan for up to 30 seats → teams can evaluate a deployment that fits their environment.
Application Scenarios
A software team with Jira-compatible workflows could evaluate ONES Project when it wants issue tracking, sprint management, custom fields, and reporting within a different deployment model. An air-gapped environment may also make self-hosted deployment options relevant.
A project group that repeatedly searches for issues tagged with informal labels may decide some categories need a stronger structure. It could use custom fields and workflows for required classifications, while keeping labels for temporary or cross-cutting themes.
A team documenting project decisions could consider ONES Wiki alongside ONES Project. Since the products are sold separately, the team can assess whether it needs project management, knowledge management, or both.
Common Challenges With Jira Labels
Similar Labels Split Search Results
Problem: Teammates create variations such as bugfix, bug-fix, and fix, making it harder to find every related issue.
Solution: Agree on a preferred label, search for existing terms before adding one, and update older issues when merging duplicates makes sense.
The Labels Field Is Missing
Problem: You open an issue but cannot see a Labels field in its details or edit screen.
Solution: Check the issue’s edit options and project layout. If the field is still unavailable, ask a Jira administrator to confirm whether it should appear for that issue type.
A Label Does Not Return Expected Issues
Problem: A search returns fewer issues than expected, even though teammates say they applied the label.
Solution: Check for spelling and capitalization differences, then inspect an affected issue to confirm the exact label value. Update inconsistent values so future searches use one agreed term.
Labels Become a Substitute for Required Fields
Problem: Teams use free-form labels for important information that must be complete or reported consistently.
Solution: Consider a custom field when a value must follow a controlled set or support a formal process. Keep labels for flexible groupings that do not need strict governance.
FAQs About Creating Jira Labels
Can I Create a Jira Label Without an Administrator?
In many Jira setups, you can create a label by entering a new value in an issue’s Labels field and saving the issue. You generally do not need to create it in a separate administration screen first. However, your ability to edit issues and the visibility of the Labels field depend on project configuration and permissions. If you cannot edit the issue, ask a project administrator for help.
Can One Jira Issue Have More Than One Label?
Yes. An issue can have multiple labels, which helps you group it in different ways. For example, a bug could have both accessibility and release-2025-04. Use additional labels only when each one adds useful context. Too many tags can make the issue harder to classify and can create more terms for teammates to maintain.
How Do I Search for Issues With a Particular Label?
Use Jira’s basic search to select Labels and enter the term, or run a JQL query such as labels = accessibility. To narrow the results to one project, add a project condition, such as project = APP AND labels = accessibility. Check the spelling and capitalization of the label if expected issues do not appear.
Can I Rename a Jira Label?
Labels are values attached to issues, so changing a label means removing the old value and applying the replacement to affected issues. Search for issues with the existing label, update those issues, and confirm the replacement label returns the expected results. Before making a change across many issues, agree on the new spelling and check whether saved filters or team instructions use the old term.
Should I Use a Label or a Custom Field?
Choose a label for an informal category that can be added as needed, such as a temporary launch theme. Choose a custom field when information must use a consistent set of values, appear in a structured workflow, or support reliable reporting. For example, a team might use labels for “customer feedback” but a required field for a defined severity level.
Conclusion
Creating a Jira label is simple: open an issue, edit Labels, enter a clear term, and save. The harder part is keeping label names consistent as more people use them.
Start with a lightweight naming convention, search before adding new terms, and use JQL or saved filters to find related issues. When a category needs required values or formal reporting, consider a custom field instead.
With a little care, labels can make cross-cutting work easier to find without turning Jira search into a guessing game.