Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • JIRA 7 Essentials
  • Toc
  • feedback
JIRA 7 Essentials

JIRA 7 Essentials

By : Patrick Li
4 (1)
close
JIRA 7 Essentials

JIRA 7 Essentials

4 (1)
By: Patrick Li

Overview of this book

Atlassian JIRA is an enterprise-issue tracker system. One of its key strengths is its ability to adapt to the needs of the organization, ranging from building Atlassian application interfaces to providing a platform for add-ons to extend JIRA's capabilities. JIRA 7 Essentials, now in its fourth edition, provides a comprehensive explanation covering all major components of JIRA 7, which includes JIRA Software, JIRA Core, and JIRA Service Works. The book starts by explaining how to plan and set up a new JIRA 7 instance from scratch for production use before moving on to the more key features such as e-mails, workflows, business processes, and so on. Then you will understand JIRA's data hierarchy and how to design and work with projects in JIRA. Issues being the corner stone of using JIRA, you will gain a deep understanding of issues and their purpose. Then you will be introduced to fields and how to use custom fields for more effective data collections. You will then learn to create new screens from scratch and customize it to suit your needs. The book then covers workflows and business processes, and you will also be able to set up both incoming and outgoing mail servers to work with e-mails. Towards the end, we explain JIRA's security model and introduce you to one of JIRA’s new add-ons: JIRA Service Desk, which allows you to run JIRA as a computer support portal.
Table of Contents (12 chapters)
close

Understanding issues

Depending on how you are using JIRA, an issue can represent different things and can even look very different in the user interface. For example, in JIRA Core, an issue will represent a task and will look like this:

Understanding issues

While in JIRA Software, if you are using the agile board, an issue can represent a story, or epic, and will resemble a card:

Understanding issues

Despite all the differences in what an issue can represent and how it might look, there are a number of key aspects that are common for all issues in JIRA, as follows:

  • An issue must belong to a project.
  • It must have a type, otherwise known as an issue type, which indicates what the issue is representing.
  • It must have a summary. The summary acts like a one-line description of what the issue is about.
  • It must have a status. A status indicates where along the workflow the issue is at a given time. We will discuss workflows in Chapter 7Workflows and Business Processes.

So in summary, an issue in JIRA represents a unit of work...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete