Explore topic-wise InterviewSolutions in .

The following are the issues that are cannot be cloned:

• Time tracking
• Issue history
• Comments and
• Links to Confluence pages

Jira is a software that allows agile project management and bug tracking. This defect tracking tool is not only used for convenience-related features like recording, reporting but it is also integrated directly with the code development environment.

Jira is an EFFICIENT tool that has the capability to track any kind of issue. Agile projects are also SUPPORTED by Jira. Jira HELPS teams report, assign, track, plan, and manage work. Thus, everything from agile software development and customer support to start-ups and enterprises is done.

References and Resources:

1. Jira 8 Essentials - Fifth EDITION by Patrick Li
2. Jira Software Essentials (Second Edition) - Published by Packt Publishing
3. Automate Everyday Tasks in Jira - by Gareth Cantrell
4. Agile VS Scrum
5. Software Testing

CLONING an issue basically MEANS copying an issue. This allows us to quickly make a copy of an issue INSIDE a similar project. The clone issue is a mirror image of the original issue. It contains similar data that is put in the original issue like the Summary, Components, Affects Versions, and so on. A clone issue is a different element from the original issue. The clone issue can similarly be connected to the original issue. 

The tasks on the original issue have no impact on the clone issue and also the other way AROUND. If a LINK is made between the original issue and the clone issue, that serves as the main connection.

Cloning an issue retains the following:

• Project
• Summary
• Issue Links
• Description
• Assignee
• Environment
• Reporter
• Attachments
• Components
• Affects Versions
• Fix For Versions
• Priority
• Issue Type
• Security

Some of the COMMON and USEFUL JIRA add-ons are as FOLLOWS:

• Slack
• Github
• Tempo Timesheets
• PagerDuty
• Jenkins-CI
• Usersnap

• For Kanban boards, the process flow is TRACKED. The work in progress (WIP) activities are maintained. Here, the team plans on increasing and DECREASING the number of issues that are to be shown in the status of the workflow.
• In the Scrum board, the progress of the sprints along with tracking of its work is CARRIED out. It is the work mode, where the team DECIDES the different types of issues that have turned backlog which is then moved to sprints as per the plan.

FOLLOWING are the limitations when editing an active WORKFLOW in Jira:

• If a workflow is active, we cannot edit the workflow name, only the description can be edited.
• We cannot delete the workflow steps.
• We cannot edit a step associated status.
• We cannot ADD a new OUTGOING transition in the case a step has no outgoing transitions Here, global transitions are not considered.
• We cannot change a step’s Step ID.

For each pair of the Jira PROJECT and issue TYPE, we can configure the FOLLOWING things:

• Project accessibility.
• Which custom fields and system an issue can use.
• The order of custom fields appears on an issue screen.
• The workflow of an issue including the statuses.
• Versions and components available for an issue.
• Permissions for what a user can do with an issue.

Jira Core is a workflow management system. This ALLOWS us to create unique processes that suit our needs. 

WORKFLOWS are the root of the system, moving PACKETS of work from one place to ANOTHER. Jira Core allows us to MAKE our workflow as easy or as complex as we need. It does this by giving us the freedom to concentrate on the work, and not on the process. The only constraints on your workflow are your processes.

JQL STANDS for Jira Query language. It is an advanced explicit way to SEARCH for issues within Jira. This consists of a FIELD, operator, value and KEYWORD. It is quite a flexible and powerful way to search for issues.

In Jira, when the prime focus of teams is to visualize the workflow and to manage the WORK in progress of the projects, Kanban boards are CREATED. An important aspect of the Kanban board is that it is GIVEN in work mode as the work planning of the projects is not done yet.

Following are the steps in order to create a Kanban board:

1. Log In to the Jira app with your credentials and go to the dashboard section.
2. Select the option of ‘Create Project’, on the Project dropdown.
3. Then, select ‘Kanban Software development’. After that click the NEXT button.

In Jira, the service desk works in the following WAY:

• The client EXPRESSES a demand for the service agents through an entryway. This can also be done via email.
• Then, a service desk sees the demand in their Jira Service Desk line. They further investigate the issue.
• The client and different MEMBERS can use the ENTRY or email to discuss about the demand with the ASSIGNED service desk agent, who works in the Jira Service Desk.
• Finally, the specialist finishes the task and the client demand is fulfilled.

The Jira Schema consists of the FOLLOWING:

• Notifications: This indicates what email someone receives when an issue is changed.
• Workflows: This indicates which WORKFLOW is used for each issue type.
• Permissions: This indicates what changes can be MADE to an issue by someone.
• Issue types: This indicates what issue types like BUG, New Feature etc. can be used in a given Jira project.
• Screens: This indicates where the fields are displayed in an issue’s screen.
• FIELD configurations: This is used to define which Field Configuration is used for each issue type.

The issues in Jira are LABELLED in order to categorize an issue within a particular SECTION. This can help to easily search with the help of labels. Label for a given issue can be initially SET at the TIME of CREATING the issue. It can also be edited within the issue.

For a particular issue, the change HISTORY section shows various activities of modifying any records. The change history displays information about the old and new field VALUES in the case of the change in any field. This also includes data of the particular person who has MADE the change and also the time at which those changes were made.

The change history has these records of the changes as GIVEN below:

• Issue field changes
• Creation and deletion of a given comment.
• File attachment changes
• Creation and deletion of a given issue link.
• Deletion of a Worklog.

After a transition is executed, the following TYPES of Post functions are carried out:

• Create an EVENT in order to trigger email notifications.
• Add a COMMENT to a given issue.
• Update the fields of an issue.
• For an issue, GENERATE the CHANGE history.

As the administrator, we can further customize the agile board in the following ways:

• Scope of the agile board: This signifies what issues and PROJECTS will be ADDED on the agile board.
• Permission of the agile board: This entails who will have access to the agile board.
• Layout of the agile board: This signifies the agile board's vertical columns and horizontal swimlanes.
• Customized filters: These PROVIDE additional ways to FILTER out the content on the agile board.

For an Agile project, the user stories are created in the following way in JIRA:

• Issue type -> Epic and Issue type –> Story linked to it. To do so, on the ‘Create Issue’ page, go to “CONFIGURE Fields”. Then select the “Epic Link” field to be included in the issue CREATION screen.
• Alternatively, you can also have a product backlog by creating one MAIN User story and having multiple sub-tasks under it.

The following are some of the configuration fields of an agile board: 

In Jira, for a particular issue, three colours NAMELY Blue, Green, and ORANGE are used to show how much time is spent on that particular issue. You can go to the section of ‘Time Tracking’ to VIEW this information. The significance of each colour is as follows:

• Blue: The blue colour is used to show the ‘Original Estimate’. This is the estimate of time to be spent in resolving an issue. You can see this field shown as ‘ESTIMATED’.
• Orange: The orange colour is for the time left to resolve an issue. You can see this field shown as ‘Remaining’.
• Green: The green colour shows the actual time that has been spent in solving given the issue till now. You can see this field shown as ‘logged’.

In order to modify a bulk issue, we NEED to use the bulk change OPTIONS - TOOL menu - then select all issues on the current page that can be USED for the bulk operations.

We get the following details when we PERFORM bulk operations:

• Workflow transition
• Delete
• Move
• Edit

In JIRA, there are a number of reports generated that are used to showcase different project statistics throughout the entire life cycle of the project. There are general reports available for analyzing issues in Jira. ALONG with this, there are also some reports for Scrum and Kanban PROJECTS.

The general reports available for analyzing the issues includes:

• Time Tracking Report
• Version Workload Report
• Workload Pie chart Report
• Created vs Resolved issue Report
• Average AGE Report
• User Workload Report
• Resolution Time Report
• Pie Chart Report
• Recently created Issue Report

For Scrum projects, the following TYPES of reports can be generated:

• Sprint Report
• Version Report
• Control chart
• Velocity chart
• Cumulative Flow diagram
• Release Burndown
• Burndown chart
• Epic Report

For Kanban projects, the following types of reports can be generated:

• Control chart
• Cumulative Flow diagram

In order to generate reports for your project, the steps given below can be followed:

1. Go to the desired ‘project dashboard’ for which you want to generate a report
2. From the left-hand side click on the Reports tab to view the different types of reports.
3. Click on the Switch report button to view the different reports.