Page History
...
More detailed information about default Jira setup for issues and field explanation can be found on the following Atlassian page: view an issue.
Issue types
Standard Issue types
An Issue Type is a way issues are classified in a Jira project and has a Icon that allows us to quickly recognize it. There are standard types that come with Jira and additional custom types.
Jira Software comes with five standard issue types (Story, Task, Bug, Subtask, and Epic) so issues can have different fields, different workflows, or both, within the same Jira project.
Issue Type | Atlassian’s Definition | Example Issue Summary (Title) |
|---|---|---|
| Functionality request expressed from the perspective of the user | As a bake sale attendee, I would like to eat brownies because I’m allergic to cake OR Make brownies for bake sale |
| Task that needs to be done | Bake a cake |
| Smaller task within a larger piece of work | Mix cake ingredients |
| Problem that impairs product or service functionality | Cake is burnt |
| Large piece of work that encompasses many issues | Make deserts for bake sale |
Relation of the issue types is as following:
If you've added sub-tasks to an issue, and need to reorder them, you can drag and drop them on the issue navigator view of the parent issue.
If you're using a board in Jira Software, you can also reorder the sub-tasks on the board view. However, these two methods are independent of each other. Reordering sub-tasks on the parent issue will not reorder tasks on an existing board, and vice-versa.
Additionally, Jira Service management adds four more standard types for support projects.
Issue Type | Atlassian’s Definition | Example Issue Summary (Title) |
|---|---|---|
| System outage or incident | The kitchen caught fire yesterday |
| General request from a user for a product or service | Fix microwave damaged during kitchen fire |
| Rollout of new technologies or solutions | Change the gas stove to an electric hot plate |
| Track underlying causes of incidents | The electric hot plate doesn’t get hot enough OR Train users on gas stove safety |
Custom issue types
Per project additional Custom issue types can exists. These were either added by Jira administrators, by additional Jira functions, or by third party apps and add-ons.
...
See Instructions under Editing dashboards how to add the filter to a dashboard.
...
Queues (Service Management only)
Customer requests are organized into queues. Queues let you quickly view, triage and assign requests as they come in.
They also provide high-level information on an issue; usually a summary, status, and customer name.
There are pre-configured queues and custom queues created by a Jira Admin/Project Admin.
Custom queues allow you to choose the name for the queue, determine what requests are filtered into the queue, and what columns appear in the queue.
Edit an existing queue
- Go to your Service Management project
- Select Queues in the right panel
- Select the target queue from the list via Switch Queues
- Click on the three dots menu in the upper right corner. You can also edit queues by using the pen icon on the upper left Queues panel.
- Select Edit queue. Edit a queue in the Queues for Jira Service Management app.
- Make changes.
- Click Save.
...
From your service project, go to Queues.
Select the queue you want to sort requests in.
Hover over the column name that you want to sort to see how it’s sorted.
Click on the column name to sort the queue. For example, clicking Summary will sort your requests in alphabetical order.
Edit multiple issues at the same time
- Go to your service desk project
- Select Queues in the right panel
- Select the target queue from the list via Switch Queues
- Select the tick boxes to select (multiple) issues
Actions will appear that can be applied to all selected issues: Link, Comment, Assign, Watch and Delete.
- Follow below procedures to change multiple requests in bulk.
Add comments to multiple requests at the same time
Rather than add a comment to a request or issue one-by-one, you can comment on many requests at the same time using bulk actions.
...
You can only add plain text to the comments, attachments cannot be added to multiple requests this way.
Assign multiple requests at the same time
This is only assignment of an issue, no allocation! This can only be done via the workflow.
...
Watch will only apply for user, you cannot add other watchers to issues via this option, this can only be done in the issue itself.
Delete multiple requests at the same time
To delete multiple requests:
...
Via search results bulk changes can be made, this option should only be used by a Jira Admin. If a bulk update is required a SD request can be submitted including the search URL.
Quick search | The quick search is the fastest way to define search criteria. However, it is less precise than other search methods for complex queries (e.g. To use the quick search: Enter your search criteria in the search box in the header bar of Jira and press Enter.
More detailed information can be found on the following Atlassian page: Quick searching |
|---|---|
Basic search | The basic search is more precise than the quick search, but easier to use than the advanced search. To use the basic search: Navigate to Issues (in header) > Search for issues, then enter your search criteria.
|
Advanced search | The advanced search is the most powerful of the three search methods. You can specify criteria that cannot be defined in the other searches (e.g. To use the advanced search: Navigate to Issues (in header) > Search for issues, then enter your search criteria.
Searching for flagged issuesThe flag for an issue is stored in a custom checkbox field named "Flagged", which has only one value: Impediment. This means that you can use this JQL query to find flagged issues: |
Filters
The Jira Issue search functionality is enhanced by the ability to save searches, called filters in Jira, for later use.
More detailed information how to work with filters can be found on the following Atlassian page: Saving your search as a filter
...
You can flag an issue to indicate that it's important, set it as impediment.
The card of a flagged issue is displayed in yellow in the Scrum backlog, Active Sprint of a Scrum board , Kanban backlog (if enabled) and, with the 'flag' icon replacing the priority icon.
- Navigate to your desired board.
- Click either Scrum backlog, Active sprints, Kanban backlog (if enabled), or Kanban board.
- Click the issue that you want to flag or unflag.
- In the Issue Detail View, select Add flag or Remove flag from the 'cog' drop-down. You can also right-click on the issue > Add flag or Remove flag.
You can also add a comment when you're adding a flag to or removing a flag from an issue. You may want to do this to indicate your reason for adding or removing the flag.
In the Issue Detail View, select Add flag and comment or Remove flag and add comment from the 'cog' drop-down. You can also right-click on the issue > Add flag and comment or Remove flag and add comment. After adding your comment, it will appear in the Comments section of the issue, with an indication that a flag was added or removed accordingly.
Board configuration
You must be a Jira administrator or a Board administrator for the board to modify its configuration. Any board user is able to view the board configuration.
...
Overview
Content Tools