Explore topic-wise InterviewSolutions in .

In JIRA, an event gives information about the status, the default template and the notification scheme and workflow TRANSITION post FUNCTION ASSOCIATIONS for the event. Basically, the events are classified into these two categories:

• A System event (Jira DEFINED events)
• Custom event (User-defined events)

VALIDATORS check that any input to the TRANSITION by a user is valid before the transition is performed. The role of validators in JIRA is to verify exactly this. The ISSUE will not progress to the DESTINATION status of the transition in case a validator FAILS.

Following are some of the POPULAR add-ons for JIRA:

• JIRA Toolkit Plugin
• JIRA Charting Plugin
• Portfolio for JIRA
• Suites UTILITIES for JIRA
• Zephyr for JIRA – Test Management
• ScriptRunner for JIRA
• Atlassian REST API Browser
• Tempo Timesheets for JIRA
• JIRA Misc WORKFLOW EXTENSIONS

Project templates ALLOW us to create new projects based on certain predefined settings. This is important so that when the project is CREATED, it will have all the necessary configurations set for us, including the following:

• Issue type scheme: An issue type scheme that contains only the relevant issue TYPES for the selected template, such as stories and epics for Scrum.
• Workflow: A specially designed workflow that makes it easier to work with the issues on an agile board.
• Screens: A set of screens that contain the necessary fields for working with agile, such as epic links to link stories to epics, and SPRINT for when tasks are added to Scrum sprints.
• Agile board: If the template is either Scrum or Kanban, an agile board is DEDICATED to the new project.

An individual unit of work in Jira is referred to as an issue. This issue could be a unit such as a STORY or an epic. EVERY issue has a field called issue type, which represents the type and use of the issue. For instance, in a Scrum project, one would have the following types of issues by default:

• Story: A story in Jira represents a SINGLE feature that is to be implemented. It is generally used in order to get the requirements from the end user's PERSPECTIVE. For this purpose, stories are often written in non-technical language. These are used for focusing on the end results of the feature.
• Epic: An epic means a big user story. This represents that the story has not been broken down into smaller and FINER requirements. In Jira, epics are mostly used to define the "theme" for various stories that will be part of it, along with the modules or the major components in a big development project.
• Bug: A bug in Jira represents a problem or a defect that needs to be fixed in a given product.
• Task: This represents a generic task that is neither a bug nor a story, but it needs to be completed.

The main user interface that an end-user will use on a daily basis for projects is called an agile board. The agile board allows us to visualize the various tasks in a project and also the available steps in the WORKFLOW of the project. Along with that, it also gives us an interactive way to transition tasks through the workflow. There are also additional features that provide a variety of FUNCTIONALITIES depending on the type of board we are using. For instance, some boards may ALLOW us to provide VISUAL cues to HIGHLIGHT potential bottlenecks, manage a backlog of features, and a lot more.

JIRA Software supports the following agile methodologies: Scrum and Kanban.

• Scrum: Scrum is an agile methodology in which the development team works in an ITERATIVE manner to complete a given project. Every sprint or ITERATION has some set scope and timeline for the project. For software development projects, Scrum is most suitable.
• Kanban: Kanban is an agile methodology that focuses on just-in-time delivery. It accomplishes this by visualizing the workflow and the tasks in progress. Kanban is MOSTLY suitable for operation teams.

The dashboard is the first DISPLAY that we see once we login to the Jira. The Jira admin can change the view of the dashboard. Along with this, they can also change the THINGS that are visible on the dashboard. A dashboard SHOWS tools and applications that assist the team members to track the progress of a PROJECT. The dashboard also contains useful information such as the issues assigned to the user that is logged in along with the user's ACTIVITY information.

The FOLLOWING are some of the benefits of using JIRA:

• It is easily customizable and extensible.
• It RUNS almost anywhere as it is platform-independent. It is recognized by quite a few well-known companies.
• We can GET the latest update on the progress of projects VIA Jira.
• It has an upfront and fair licensing policy.

Since Jira is used to track the issue and transitions in the development life cycle of the software, the workflow is like a set of software-related activities which help in performing these OPERATIONS. The link between these 2 states is CALLED a transition. The issue moves from one transition state to another state. The status is used to DEFINE the NATURE of the WORK that is completed by the tester.

In the JIRA workflow, the important phases that occur are given below:

• To Do
• In progress
• Finally done