How to Create a Label in Jira: Quick Step-by-Step Guide
Need to organize Jira issues faster? Learn how to create a label in Jira, apply it, and find tagged issues. Click to discover the quick steps.
Jira labels can turn a crowded issue list into something you can sort and search quickly. But if you cannot find where to add one, or you create several spellings for the same idea, labels become more confusing than helpful.
That can leave your team filtering for “urgent” while important issues are tagged “Urgent” or “urgency.” The good news is that adding a label usually takes only a few clicks, and a simple naming rule can keep labels useful as your project grows.
Here’s how to create a label in Jira, apply it to an issue, and find issues that share it. I’ll also cover common label problems so you can avoid messy results later.
Create a Jira label in a few steps
Open an issue, find its Labels field, enter a label, and confirm it. Jira creates the label when you add it to an issue; you generally do not need to create it in project settings first.

1. Open the issue you want to label
Go to your Jira project and select the issue. You can add a label to an issue you created or one you have permission to edit.
2. Find the Labels field
Look for Labels in the issue details. Depending on your Jira layout, it may appear in the main issue view or inside the Edit dialog.
If you cannot see the field, open the edit view and check there. Some Jira administrators customize which fields appear on screens.
3. Enter and confirm the label
Click the Labels field, type a short label such as mobile-bug, then press Enter or select the matching suggestion. Jira may show labels already used in the project.
Use a new value if you need a new label. Avoid spaces; use a hyphen or underscore to join words, such as release_candidate.
4. Save and check the issue
If you are editing the issue in a dialog, select Update to save your change. Some Jira views save inline edits automatically after you confirm the label.
Check the issue details to make sure the label appears. If it does not, reopen the issue and confirm that the change was saved.
Choose labels that stay useful
A label works best when it describes a clear, reusable category. For example, a team might use mobile for mobile issues and release-3-2 for work tied to a particular release.
But here's the truth: labels are easy to add and just as easy to scatter. A short naming convention can prevent near-duplicates and keep filters meaningful.
Set a simple naming convention
Decide whether your team will use lowercase, hyphens, or underscores. Then share a few examples so everyone can follow the same pattern.
- Use
customer-feedback rather than mixing customer feedback and customer_feedback.
- Choose labels for categories that can apply to multiple issues.
- Use a Jira component or another structured field when the information needs fixed options or formal reporting.
Check existing labels before adding one
As you type, review Jira’s suggestions. If a suitable label already exists, select it instead of creating another version.
For example, if the project already uses performance, avoid adding perf for the same type of work. Consistent terms make searches and reports easier to interpret.
Apply labels to multiple issues
If several issues need the same label, bulk editing can save time. For example, you might label a group of related issues release-3-2 before tracking their progress together.
Use Jira’s bulk change flow
Find the relevant issues with a search or filter, select the issues you want to update, and choose the bulk change option. Available actions depend on your Jira permissions and configuration.
Choose the option to edit issues, then update the Labels field. Review the selected issues before confirming the change, especially if your search could include work outside the intended project or release.
For a small number of issues, adding the label individually may be safer. A quick review helps you catch an overly broad selection before the same label appears on unrelated work.
Find issues by label
Once a label is attached to issues, you can use it to narrow a project search. This is useful when a team wants to review a category such as accessibility or customer-feedback.
Search with Jira filters or JQL
In Jira’s issue search, select the Labels field and choose the value you want. If you use JQL, a basic search looks like this:
labels = "accessibility"
To find issues that have one of several labels, you can use a query such as:
labels in ("accessibility", "mobile")
Save a useful search as a filter if you expect to use it again. For example, a team can keep a filter for accessibility issues and return to it during regular reviews.
Fix common label problems
Most label issues come down to field visibility, permissions, inconsistent naming, or a search that does not match the saved label. Here's why: each problem has a different fix, so check the details before adding another label.
The Labels field is missing
First, open the issue’s edit view and look for the field there. If it is still missing, ask your Jira administrator whether the field is available on the relevant issue screen.
You cannot add or edit a label
Your Jira permissions may not allow you to edit that issue. Confirm that you can make other changes to it, then ask a project administrator for help if needed.
Your search returns no issues
Check the spelling and punctuation of the label on an issue. A search for mobile-bug will not find issues labeled mobile_bug.
Try selecting the label from Jira’s search suggestions instead of typing it from memory. This can reveal whether the project uses a slightly different value.
Duplicate labels are accumulating
Agree on a preferred spelling and tell teammates which label to use. If you need to clean up older labels, identify affected issues and update them carefully rather than deleting or replacing values blindly.
ONES.com is a unified platform for project management and knowledge management, powered by ONES Assistant. ONES Project is its project-management product and a Jira alternative; ONES Wiki is its knowledge-management product and a Confluence alternative, and the products are sold separately.

Core capabilities
- Workflows feel familiar: Teams using Jira-compatible workflows can bring established issue processes into ONES Project, reducing the learning curve when evaluating another platform.
- Less plugin dependence: Built-in reporting, automation, and sprint management can reduce reliance on separate plugins for common project-management needs.
- Workflows fit the team: Custom workflows and fields let teams track details that do not fit a default setup, such as review stages or a hardware model.
- Reports show project progress: Built-in reporting gives teams a way to review work without assembling a separate reporting process for each project.
- Sprints support iterative work: Sprint-management capabilities help teams plan and follow short delivery cycles within the project environment.
- Deployment fits operational needs: Teams can choose Cloud, On-Premise, Private Cloud, or Air-gapped deployment, depending on their environment and requirements.
- Self-hosting retains feature parity: ONES offers full feature parity between its cloud and self-hosted versions, so a self-hosted deployment does not mean giving up feature access.
- Smaller teams can try it: The free offering supports up to 30 seats, giving a team room to evaluate the platform with a limited group.
Where it can fit
A software team moving from Jira could use ONES Project to manage issues, sprints, custom workflows, and reports in one project-management environment. If the team relies on labels, it can establish a consistent label convention as part of its workflow setup.
A team with strict network requirements might evaluate the On-Premise, Private Cloud, or Air-gapped deployment options. A separate group that needs shared knowledge management could consider ONES Wiki, while keeping in mind that it is a separate product.
The best part? You can assess the fit against your actual project practices, including permissions, required fields, and reporting needs, before deciding whether a change makes sense.
Common challenges and practical fixes
Labels are being used for information that changes often
Problem: People add a new label for every short-lived status, such as waiting-for-review, even when the team already tracks status elsewhere.
Solution: Keep labels for reusable categories. Use Jira’s status or another structured field for information that changes as work moves through a process.
Different teammates use different spellings
Problem: Search results split across labels such as ui-bug, UI-bug, and user-interface-bug.
Solution: Pick one preferred term and share a short naming guide. When adding a label, choose an existing suggestion whenever it matches your intent.
Labels are added to too many issues
Problem: A broad label applied during a bulk change can make a filter noisy and less useful.
Solution: Review the selected issues before confirming a bulk edit. Start with a narrow search, then check that each result belongs in the category.
A label seems impossible to remove
Problem: You may be editing the wrong issue field or may lack permission to update the issue.
Solution: Open the issue, remove the label from the Labels field, and save the change. If Jira blocks the edit, ask an administrator to check your permissions.
Frequently asked questions
Do I need to create a Jira label in project settings first?
Usually, no. A Jira label is generally created when you add it to an issue. Open the issue, enter the value in the Labels field, and confirm it. Jira may suggest labels already in use, but you can enter a new value if you have permission to edit the issue. Your organization’s Jira configuration may affect which fields are available.
Can one Jira issue have more than one label?
Yes. An issue can have multiple labels, which can help you group it in more than one useful way. For example, a single issue could have mobile and accessibility. Keep the set focused, though. Too many overlapping labels can make searches harder to understand and maintain.
Can I use spaces in a Jira label?
It is clearer to use a single label term or join words with a hyphen or underscore, such as release-candidate or release_candidate. This makes labels easier to scan and use in searches. Before settling on a format, check existing project labels and follow the team’s convention.
How do I remove a label from an issue?
Open the issue, edit the Labels field, and remove the value you no longer want attached. Save the change if Jira presents an edit dialog; inline views may save after you confirm the edit. Removing a label from one issue does not necessarily remove it from other issues that use the same label.
Conclusion
Adding a Jira label is straightforward: open an issue, enter a clear value in its Labels field, confirm the change, and save if required. Then use a consistent naming convention so labels remain useful in searches and filters.
If the field is missing, check the issue’s edit view and your permissions. If you are labeling many issues, review the selection before applying a bulk change. A few careful habits can keep issue categories clear as your project grows.
You might be wondering: is a label enough for the information your team needs to track? Use labels for flexible grouping, and consider structured fields or workflow settings when you need controlled values and repeatable project processes.