Need help working with issues? In Jira Software, issues help you manage code, estimate workload, and keep track of your team. On this page, you'll find a quick overview for everything that you can do with an issue.
Boards can display up to 5000 issues at a time. If your board is trying to display more than 5000 issues at once, you'll receive an error message, and be prompted to update your filters.
What is an issue?
Different organizations use Jira to track different kinds of issues, which can represent anything from a software bug, to a project task, or a leave request form.
Issues are the building blocks of any Jira project. An issue could represent a story, a bug, a task, or another issue type in your project.
Here's an issue in a Scrum backlog:
- Selected issue: Select an issue to view its details.
- Backlog: Estimate issues and plan your sprints.
- Issue actions: Move an issue, clone it, log time spent working on it, and perform other actions.
- Issue details: See the assignee and description, make comments, and add content to the issue.
Here's an example issue:
- If you're a project admin, choose ••• > Configure to change the layout of fields in the issue view.
- You can see related commits, builds, and pull requests to help you evaluate the development status of your issue. See Viewing the development information for an issue.
Project and issue keys
Issue keys are unique identifiers for every piece of work you track with Jira. They are easily recognizable and quick to remember.
You'll see issue keys:
- On issues themselves, as a label
- In search results and saved filters
- On cards on your boards or in a project's backlog
- In links connecting pieces of work
- In the issue's URL
- Anywhere you need to reference the work you're tracking
Issue keys are made up of two parts:
- The project key (SMART in the screenshot above)
- A sequential number
Project keys are a series of alphanumberic characters that describe to people across your Jira site what pieces of work are related to your project. They're the most memorable and recognizable piece of an issue's identifier. For example, our team is codenamed Donut World. We use the project key "DONUT" to help people across Atlassian know and recognize work that relates to our team.
Project admins can create and assign their project's key when they create a new project. Based on the project's name, Jira suggests a recognizable key. If you're a project admin, you can customize this while creating a project by selecting Advanced options. You can also update it in the project's settings. They must be at least 2 characters long and start with an uppercase letter. Read more about editing a project's details.
If you have admin permissions, you can configure issues, create new issue types, manage custom fields, and more.