This controls the types of issues that users can create for the project. For example, this may include bugs, improvements, and tasks.

Issue types will be covered in Chapter 4, Issue Management.

This controls the workflow issues that we will go through. Workflows consist of a series of steps that usually mimic the existing processes that are in place for the organization.

Workflows will be covered in Chapter 7, Workflow and Business Process.

Screens are what users see when they view, create, and edit issues in Jira.

Screens will be covered in Chapter 6, Screen Management.

These are what Jira uses to capture data from users when they create issues. Jira comes with a set of default fields and the Jira administrator is able to add additional fields as needed.

Fields will be covered in Chapter 5, Field Management.

Project administrators can define roles in the project and assign users to them. These roles can then be used to control permissions and notifications.

Roles will be covered in Chapter 9, Securing Jira.

As we have already seen, permissions define who can perform certain tasks or have access in Jira.

Permissions will be covered in Chapter 9, Securing Jira.

Jira allows users to control who can view the issues they created by selecting the issue security level.

Issue security will be covered in Chapter 9, Securing Jira.

Jira has the ability to send out email notifications when certain events occur. For example, when an issue is updated, Jira can send out an email to alert all users who participate about the issue of the change.

Notifications will be covered in Chapter 8, Emails and Notifications.