Jira Issue Keys: A Guide to Their Format, Meaning, and Use
What does a Jira issue key mean? Learn its format and how to use it to find, link, and track work. Click to discover.
A Jira ticket can be easy to find on screen but surprisingly hard to discuss when its identifier is missing. If a teammate says “the login bug” or pastes a link that no longer works, you may waste time searching, checking duplicates, or updating the wrong issue. The confusion often comes down to a small code such as WEB-123: the Jira issue key. But here's the truth: that key is more than a label. It helps you locate, link, discuss, and track work across Jira and connected tools. Once you know how its parts fit together, you can read keys quickly, spot common mistakes, and handle changes with less guesswork. Here’s a practical guide to what Jira issue keys mean and how to use them reliably.
What a Jira issue key means
A Jira issue key is the human-readable identifier for an issue, usually written as a project key, a hyphen, and a number, such as WEB-123. The project key identifies the Jira project, while the number identifies that issue within the project.

Reading the parts of a key
In WEB-123, WEB is the project key and 123 is the issue number. The project key is commonly made of uppercase letters, though its format can depend on Jira configuration. The number is assigned within the project and is not a count of every issue across your Jira site.
For example, WEB-123 and OPS-123 refer to different issues in different projects. The matching number does not make them duplicates. Jira identifies each issue using the full key.
Key, issue ID, and summary are different
The key is designed for people to read and share. An issue’s summary is its descriptive title, such as “Reset password link expires early.” Jira also has an internal issue ID, which may appear in API responses and integrations.
Think of the key as a convenient address and the summary as a brief description of what you’ll find there. If you need to refer to a specific issue in a conversation, use its key rather than relying on a summary that could resemble another issue.
How Jira issue keys are created and used
Jira assigns a key when an issue is created in a project. You can find it in the issue view, use it to open the issue directly, or include it in a message so colleagues can identify the exact work.
- Find the project key. Open an issue in the relevant project and look at its identifier. In
WEB-123, the project key is WEB.
- Use the complete key. Copy the project key, hyphen, and issue number together. Leaving out any part may make the reference unclear.
- Search or open the issue. Enter the full key in Jira search, or use it in the browser address shown for the issue.
- Share the key in context. Add it to a message or task update, such as “Please review
WEB-123 before Thursday’s release.”
- Check the issue details. Confirm the summary, project, and status before acting, especially when the reference came from an older conversation.
For example, a developer can mention API-58 in a code review, while a project lead can use the same key in a status update. The key makes the reference precise even when those people use different tools.
Using keys in links and integrations
Jira commonly lets you open an issue with a URL containing its key, such as https://example.atlassian.net/browse/WEB-123. Your own site address will differ, but the key is the useful part to recognize.
Integrations and API calls may accept an issue key, an internal ID, or both. For instance, Jira’s REST API can use a key in an issue endpoint. If you are building an integration, check which identifier the specific endpoint expects.
When an issue key can change
A key is stable enough for everyday reference, but it is not always permanent. Moving an issue to another project can change the project portion of its key. Changing a project key can also affect the keys associated with issues in that project.
Suppose an issue moves from the WEB project to PLAT. Its key may change from WEB-123 to a key using the destination project and its issue number. The exact result depends on the Jira operation and configuration.
What to check after a move or project-key change
Update active references in team messages, release notes, and connected tools when an issue’s key changes. Older links may still redirect or resolve in some circumstances, but you should not assume every integration will recognize an earlier key.
If an old reference fails, search Jira using the issue summary, project, or relevant details. Then confirm that the result is the intended issue before replacing the key in any ongoing work.
Common mistakes and ways to avoid them
Small typing errors can send a teammate to the wrong issue or make a useful reference impossible to find. A quick check of the project portion and issue number can prevent unnecessary back-and-forth.
- Sharing only the number: “123” could refer to many issues. Share the complete key, such as
WEB-123.
- Confusing a key with a summary: A title describes the work, while the key identifies the issue. Include both when a conversation needs context.
- Assuming keys are globally sequential: Issue numbers belong to projects. Check the project key as well as the number.
- Copying an outdated key: A move or project-key change may make an older reference stale. Open the link and verify the current issue details.
- Ignoring permissions: A valid key does not guarantee that every teammate can view the issue. Check project access if someone cannot open it.
Jira issue tracking with ONES.com
ONES.com brings project management and knowledge management together as one platform, with products sold separately. ONES Project is its project management product and a Jira alternative for teams that need structured issue tracking, adaptable workflows, and deployment choices.

If your team is reviewing how it organizes work, focus on the everyday friction: too many plugins, workflows that are difficult to adjust, or deployment requirements that Jira does not fit. The capabilities below show how ONES Project can address those needs without assuming that a Jira issue key will carry over unchanged.
Core capabilities
- Pain: Jira workflows rely on several add-ons. ONES capability: Jira-compatible workflows and built-in reporting. Result: Teams can manage common work patterns with fewer plugins.
- Pain: A team’s process does not match its default issue flow. ONES capability: Custom workflows. Result: Work can follow stages that reflect the team’s actual review and approval steps.
- Pain: Issue forms lack the details a team needs. ONES capability: Custom fields. Result: Teams can capture relevant information, such as a service area or release target.
- Pain: Sprint planning and delivery are difficult to track. ONES capability: Sprint management. Result: Agile teams can organize planned work and follow sprint progress.
- Pain: Repeated manual updates slow down issue handling. ONES capability: Automation. Result: Teams can reduce routine actions by setting up suitable rules.
- Pain: Project leads lack a clear view of progress. ONES capability: Built-in reporting. Result: Teams can review project activity without relying on a separate reporting add-on for every need.
- Pain: A team has strict hosting or network requirements. ONES capability: Cloud, On-Premise, Private Cloud, and Air-gapped deployments. Result: The team can choose a deployment model suited to its environment.
- Pain: Self-hosting risks losing capabilities available in the cloud. ONES capability: Feature parity between cloud and self-hosted versions. Result: Teams can select an appropriate deployment without giving up feature access.
Application scenarios
Scenario one: an engineering team reducing add-on dependency. A team uses custom issue fields, sprint management, and reports to coordinate development. With ONES Project, it can evaluate which needs are covered natively and reduce reliance on multiple plugins.
Scenario two: an organization with restricted network access. A team that cannot use a public cloud service can assess an On-Premise, Private Cloud, or Air-gapped deployment. It can plan project workflows around its requirements while keeping issue tracking in a controlled environment.
ONES.com offers a free plan for up to 30 seats. When evaluating it as a Jira alternative, map your current workflows and integrations first. Confirm which issue references need to be retained or updated during any transition.
Common challenges when working with issue keys
- Problem: A teammate cannot open a key you shared. Solution: Check that the key is current, then verify that the teammate has permission to view the project and issue.
- Problem: A key in an older message no longer works. Solution: Search Jira by the issue’s summary or project details. Confirm the match, then share its current key.
- Problem: Several issues have similar summaries. Solution: Use the complete key in messages and confirm the project before changing status or assigning work.
- Problem: An integration rejects a valid-looking reference. Solution: Check whether the integration expects a Jira key or an internal issue ID. Confirm the expected identifier format for that operation.
Frequently asked questions
What does a Jira issue key look like?
A Jira issue key commonly looks like WEB-123. The letters before the hyphen identify the project, and the number after it identifies an issue within that project. Project keys are usually uppercase, though the exact allowed format can depend on configuration. Use the complete key when searching for an issue or sharing a reference with a teammate.
Is a Jira issue key the same as an issue ID?
No. The issue key is the readable identifier people commonly use, such as WEB-123. Jira also assigns an internal issue ID, which may appear in API responses or technical integrations. These identifiers serve different purposes, so check what a particular API or integration requires. For everyday team communication, the full issue key is usually the clearest reference.
Can a Jira issue key change?
Yes, it can change in situations such as moving an issue to another project or changing a project key. What happens to the full key depends on the operation and Jira configuration. If an older reference stops working, search for the issue and verify its summary and project. Then share the current key with anyone who needs to find it.
How do I find an issue using its key?
Enter the complete key in Jira search, or open the issue’s URL if you have it. A URL commonly includes a path such as /browse/WEB-123. Check that the result shows the project and summary you expect. If Jira does not show the issue, confirm the spelling and check whether your account has permission to view it.
Are Jira issue numbers unique across every project?
No. The number is associated with a project, so two projects can each have an issue numbered 123. The project key distinguishes those issues: WEB-123 and OPS-123 point to different work. That is why sharing only the number can cause confusion. Include the full key whenever you want someone to locate a specific Jira issue.
Conclusion
A Jira issue key combines a project key and issue number to give each issue a clear, shareable reference. Use the full key, verify the issue before acting, and refresh older references after project changes. If your team is reassessing its issue-tracking setup, compare its workflow and deployment needs with options such as ONES Project. A few seconds spent checking the key can save a longer search later.