Working with issues
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.
We're rolling out a new issue view, with a consistent appearance across Jira and one screen to view and edit. It looks a little different and some procedures have changed slightly, so take a look at our info page to see what's new and get the latest updates. To turn the new issue view on or off in Jira Software projects for now, head to Your profile and settings ( and toggle the switch for the New Jira issue view. ) > Personal settings
Here's an issue in the full-page view:
- Quick add buttons: Add attachments, subtasks, linked issues, and content from Atlassian Marketplace apps.
- Watch and more actions: Watch the issue, and perform other issue actions like move and clone.
- Transition issues: Quickly get from to-do to done, and any status or workflow step in between.
- Contextual information: Issue labels, components, time tracking, and more.
- Docked comment bar: Always there, so you can quickly add a comment no matter how far you've scrolled.
Note the following details:
- The issue detail view may show different fields to the full view, if it has been customized by your administrator.
- To see the full view, open the issue in a new tab/window by clicking the issue key.
Most information on an issue is self-explanatory. Here are a couple of things to be aware of though:
This panel will be shown on the issue, if your administrator has set Time Tracking to 'Remaining Estimate and Time Spent'. If an issue has sub-tasks, the Remaining estimate for the issue plus sub-tasks is rolled up into the parent issue.
The History tab of an issue records the following information: creator of the issue (this may be the same as the reporter, but can be distinct), changes to an issue field, attachment of a file, deletion of a comment, deletion of a worklog, creation or deletion of an issue link.
The Activity tab has the same information, plus additional information, such as comments. However, this may load more slowly, especially if there has been a lot of activity on the issue.