35+ JIRA Interview Questions & Answer [AGILE TRICKS] | 2020
JIRA Interview Questions and Answers

35+ JIRA Interview Questions & Answer [AGILE TRICKS]

Last updated on 04th Jul 2020, Blog, Interview Questions

About author

Kannan (Sr QA Engineer - Jira )

High level Domain Expert in TOP MNCs with 8+ Years of Experience. Also, Handled Around 20+ Projects and Shared his Knowledge by Writing these Blogs for us.

(5.0) | 15212 Ratings 3802

These JIRA Interview Questions have been designed specially to get you acquainted with the nature of questions you may encounter during your interview for the subject of JIRA . As per my experience good interviewers hardly plan to ask any particular question during your interview, normally questions start with some basic concept of the subject and later they continue based on further discussion and what you answer.we are going to cover top 100 JIRA  Interview questions along with their detailed answers. We will be covering JIRA  scenario based interview questions, JIRA  interview questions for freshers as well as JIRA  interview questions and answers for experienced. 

1. What is JIRA?


JIRA is an issue tracking product developed by Atlassian which allows bug tracking and agile project management. The name “JIRA” is inherited from the word Gojira, the Japanese word for Godzilla, which is a reference to a competitor Bugzilla.

2. Why is JIRA used?


Atlassian JIRA is an issue tracking and agile project management tool which allows us to track any project by following a proper workflow. Following are the reasons behind using JIRA.

  1. JIRA is a platform independent that could run anywhere
  2. JIRA can be run anywhere
  3. In JIRA, a workflow can be easily customized based on our requirement
  4. JIRA acts as an issue tracking as well as project management tool
  5. JIRA allows us to track the progress of a project from time to time

3. What are the differences between JIRA and Bugzilla?


JIRA and Bugzilla are the two bug tracking tools that are widely being used by several organizations for quite some time now.

JIRA is a commercial toolBugzilla is an open source tool
JIRA is a user friendly tool compared to BugzillaBugzilla is not so friendly tool compared to JIRA
Drag and drop issue prioritization is available in JIRADrag and drop issue prioritization is not available in Bugzilla
JIRA has configurable link types with user-defined semantics. JIRA also has pluggable remote issue links, that allow to link an issue to any other entity outside JIRABugzilla has only one link type: blocks/depends, plus a Bug ID custom field
Unlike Bugzilla, JIRA allows to define multiple workflows which are applied based on the issue’s Project and TypeUnlike JIRA, Bugzilla can let users select the initial status of a new issue
Custom field types available in JIRA are too many to list, and even more custom field types available from pluginsCustom field types available in Bugzilla are Text fields, Multi-selection, Drop-down, Date/time, Bug ID
JIRA allows conditional configuration based only on Project and Type fieldsBugzilla lets you show/hide the whole custom field or specific values based on the value of some other field
JIRA lacks advance-level search options. JIRA has flexible JQL language (JIRA Query Language) that allows you to build arbitrary boolean expressionsBugzilla comes with a powerful advanced search option

4. Can Jira be used for test case management?


Although JIRA was not designed to serve as a Test Case Management, it can be configured to support test case management in two different ways.

You can either change native components in JIRA to meet test case management needs or you can use one of the add-ons available in Atlassian Marketplace (Example: Zephyr of JIRA)

5. What is a workflow in JIRA?


Workflow is defined as a series of sequential tasks that need to be completed in order to reach a certain goal.

A workflow in JIRA is defined as a series of sequential tasks (such as create/open a bug, Work in progress, and completed/closed) involved in the life cycle of a bug or an issue.

Create: Create an issue or bug

Work in progress: Series of actions performed to fix the issue

Closed: Completion of the issue after verification

6. Explain working with workflows in JIRA?


A JIRA workflow is a set of statuses and transitions that an issue travels through during its lifecycle and normally represents processes within your organization. There are pre-defined built-in workflows that can’t be edited; however, you can copy and utilize these workflows to create your own.

7. What are the limitations when editing an active workflow?


Limitations apply when editing the draft for an active workflow:

  • It is not possible to edit the workflow name
  • Workflow statuses cannot be deleted
  • If a status has no outgoing transitions, it cannot have any outgoing transitions added, regular or global
  • The step ID cannot be changed

8. What is a Workflow designer in JIRA?


The workflow designer in JIRA is a graphical tool that enables you to see the layout of your workflow and to create and modify a workflow’s procedures and transitions.

  • You can manage status and transitions: add, click and drag, or select to edit properties to rename, or delete
  • You can add a global transition that permits different status in the workflow to transition to the selected status. Select Allow all statuses to transition to this one in the properties board for the transition.
  • You can change the screen that a transition uses.
  • You can configure advanced transition options such as conditions, triggers, validators, and post functions.

9. How does a service desk work in JIRA?


Here is how Customers and Service desk agents work together to resolve a request in JIRA.

  1. Your customer submits a request to service agents through a portal or by email
  2. Service desk agents see the request in their JIRA Service Desk line and investigate the issue.
  3. Your customer and other participants utilize the portal or email to discuss the request with the service desk agent, who works in JIRA Service Desk.
  4. Your service agent completes the request and your customer is satisfied.

10. How are reports generated in JIRA?


Steps to follow to generate reports in JIRA are as follows:

Step 1: Navigate to the desired board and click Reports. You can find different types of reports.

Step 2: Click Switch report to view a different report.

Step 3: Click on the switch report option to view a different report

11. What are the types of reports generated in JIRA?

Ans: JIRA provides different types of reports within a project which are used to show the project statistics throughout the project life cycle. There are reports to analyze issues as well as reports for Scrum and Kanban projects.

12. Name some reports generated by Kanban projects in JIRA.


The reports generated by any Kanban project in JIRA are

  • Control chart
  • Cumulative Flow diagram

13. Name some reports generated by Scrum projects in JIRA.


The reports generated by any Scrum project in JIRA are

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

14. Name some reports generated in JIRA for the issues tracking and analysis.


Following are the general reports generated as and when required for analyzing issues:

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

15. What is an issue in JIRA?


Different organizations use JIRA to track various types of issues, which can represent anything from a software bug, to a project task, or a leave request form.

Issues are the building blocks of any JIRA project. An issue could represent a story, a bug, a task, or another issue type in your project.

16. Explain how an issue is created in JIRA.


Let’s see step by step how an issue is created in Atlassian JIRA.

  1. Click Create at the top of the screen to open the Create Issue dialog box.
  2. Select the relevant Project and Issue Type in the Create Issue dialog box.
  3. Type a Summary for the issue and complete any appropriate fields (required fields are marked by an asterisk)
    Note: Make sure you check they’re all correct before creating the next issue.
  4. When you are satisfied with the content of your issue, click the Create button.

17. What are the color indicators in JIRA and mention their significance?


There are three color (Blue, Orange & Green) indicators in JIRA. Issue tracking becomes easy with different color representations. These three colors are used to denote the amount of time spent on any particular issue.

  • Blue Color: Blue color denotes Original Estimate i.e., the estimated time to resolve an issue
  • Orange Color: Orange color denotes Remaining Estimate i.e., the remaining time to resolve an issue
  • Green Color: Green color denotes Time spent or Logged i.e., the total time spent to resolve the issue

18. What elements are included under the change history for any particular issue?


Change history for any particular issue includes the following

  • Creation and deletion of a comment
  • Creation and deletion of an issue link
  • Deletion of worklog
  • Attachment of a file
  • Issue field changes

19. How to view change history for any issue in JIRA?


The change history for any issue can be viewed in JIRA by following steps:

  • Open any issue.
  • Click on the ‘History’ tab present in the ‘Activity’ section.

20. How can an issue be shared in JIRA with other users?


There is a share option available on the issue description page in JIRA. An issue can be shared with other users using this share option. Once a share option is clicked, it will ask you to provide “Username or Email” and “Note”

    Subscribe For Free Demo

    21. Why is an issue labeled in JIRA?


    Labeling an issue in JIRA allows you to find which category an issue belongs to. Issues can be easily searched with the help of labels. Labels can be initially set at the time of creating the issue. It can also be modified if required.

    22. How is an issue linked in JIRA?


    Linking means establishing the relationship between the two. In JIRA, an issue can be linked with other issues on either the same or different JIRA servers.

    An issue can be linked with other issues as follows

    • An issue may relate to another issue
    • An issue may duplicate another issue
    • An issue may block another issue

    23. What is the use of Move Issue wizard in JIRA?


    Move Issue wizard enables you to specify another project in your JIRA instance. The Move Issue wizard permits you to change certain attributes of the issue such as Issue Type, Issue Status, and Custom Fields.

    • Issue Type: If your issue is a custom issue type that does not exist in your target project, you must choose a new issue type.
    • Issue Status: If you have assigned a custom status to your issue, and it does not exist in your target project, you must select a new issue status for your issue.
    • Custom Fields: If you have defined required custom fields for your issue that does not exist in your target project, you must set values for them.

    24. How to schedule an issue in JIRA?


    To schedule an issue, populate its Due date field. This can be done either when creating an issue, or at a later stage by editing the issue. Only users with the schedule issues permission can populate the Due date field.

    25. How project details are listed in JIRA?


    All the projects have some attributes that are displayed under the project summary section.

    The list of attributes in JIRA is

    • Nature of the project
    • Keys for the project
    • Components
    • Version

    26. What are the issues types in JIRA?


    Each Jira application comes with default issue types. You can use these default issue types or create your own to suit the needs of your projects and teams.

    Here’s an example of specific issue types within each Jira application:

    Jira Core default issue types:

    • Task – Task that needs to be done
    • Subtask – Smaller task within a larger piece of work

    Jira Software default issue types

    • Story – Functionality request expressed from the perspective of the user
    • Bug – Problem that impairs product or service functionality
    • Epic – Large piece of work that encompasses many issues

    Jira Service Desk default issue types

    • Incident – System outage or incident
    • Service request – General request from a user for a product or service
    • Change – Rollout of new technologies or solutions
    • Problem – Track underlying causes of incidents

    27. What is Cloning an Issue in JIRA?


    Cloning, or copying, an issue lets you quickly create a duplicate of an issue within the same project. The clone issue is a replica of the original issue, containing the same information stored in the original issue — e.g. Summary, Affects Versions, Components, and so on. The clone issue can likewise be connected to the original issue.

    A clone issue is a different entity from the original issue. Tasks of the original issue have no impact on the cloned issue and vice versa.

    A clone issue retains the following information:

    • Summary
    • Description
    • Assignee
    • Environment
    • Priority
    • Issue Type
    • Security
    • Reporter
      (If you do not have the Modify Reporter permission, the clone issue will be created with you as the Reporter.)
    • Components
    • Affects Versions
    • Fix For Versions
    • Issue Links (optional)
    • Attachments (optional)
    • Project
      (Once the clone has been saved, you can move it to another project as described in Moving an Issue.)

    The content of custom fields is also cloned.

    28. What are the things that are not cloned from the original issue?


    Things that aren’t cloned:

    • Time tracking
    • Comments
    • Issue History
    • Links to Confluence pages

    29. How to create a clone of an issue?


    Follow the steps mentioned below to create a clone of an issue

    Open any JIRA issue which you wish to clone

    • Select More > Clone. The Clone Issue screen will appear,
    • You can edit the clone issue’s Summary if you wish.
    • If the issue contains links to other issue(s), you can select whether or not to include the links in the new clone issue.
    • If the issue contains sub-tasks, you can select whether or not to create the sub-tasks in the new clone issue.
    • If the issue contains attachments, you can select whether or not to include the attachments in the new clone issue.
    • Click Create.

    30. What is a Sub-task in JIRA?


    Sub-task is the way of splitting up a parent issue into a number of smaller tasks that can be assigned and tracked separately. All the sub-tasks to a parent issue are summarised on the parent issue’s main screen. Sub-tasks always belong to the same project as their parent issue.

    Course Curriculum

    Learn Expert-led JIRA Courses Taught By Industry Experts

    Weekday / Weekend BatchesSee Batch Details

    31. How is a sub-task created in JIRA?

    • Navigate to the issue you would like to be the parent issue of the sub-task you are about to create.
    • Select More > Create Sub-Task. You will see the Create Subtask screen.
    • Fill in the details as needed, and then click Create at the bottom of the page.

    32. How to create a Kanban board in JIRA?


    Let’s see step by step process of creating Kanban board in JIRA

    • Log In to the JIRA application using valid credentials and get navigated to the dashboard.
    • Click on Project dropdown and select Create Project.
    • Select Kanban Software development and click Next.
    • Enter all the necessary details and click Create.

    33. Mention some of the popular JIRA add-ons?


    Some of the popular JIRA add-ons are as follows

    • Zephyr for JIRA – Test Management
    • Jenkins – CI
    • GitHub
    • Slack
    • Atlassian REST API Browser
    • ScriptRunner for JIRA
    • JIRA Toolkit Plugin
    • Tempo Timesheets

    34. How to define a component in JIRA?


    Components are sub-sections of a project. They are utilized to assemble issues within a project into smaller parts.

    Managing a project’s components

    • Sign in to JIRA as a project administrator.
    • Choose Settings > Projects > and click the name of a project. The Project Summary page will appear.
    • Choose Components in the left menu. The Components page is shown, demonstrating a rundown of Components and every Component’s information.

    35. How to delete a component in JIRA?


    To delete a component in JIRA,

    1. Navigate to components screen, hover over the relevant component to display the Delete button.
    2. You will be prompted to connect these issues with another component if you wish.

    36. What are the Version control systems we can integrate with JIRA?


    JIRA can be integrated with version control systems such as Git, Subversion, Visual SourceSafe, etc.,

    37. Explain how you can edit multiple issues at the same time?


    Editing multiple issues at the same time can be done by performing a bulk operation. To perform this bulk operation, you will need the global Make bulk changes permission and the relevant permission for each project.

    Bulk operations available in JIRA are as follows

    • Transition multiple issues through a workflow
    • Delete multiple issues
    • Move multiple issues
    • Edit multiple issues
    • Watch or stop watching multiple issues

    38. What is Zephyr for Jira?


    Zephyr for JIRA is an add-on application that provides highly sophisticated test management capabilities right inside JIRA.

    39. What is the importance of JIRA Dashboard? How to create a new Dashboard or customize the existing dashboard in Jira?


    A dashboard is the first page you can see when you logged in to the JIRA application.

    This is a default dashboard that is common for all JIRA users but you can create your own dashboard as per your requirement.

    You can design your personal dashboard by adding different gadgets.

    Follow the below steps to create a dashboard in JIRA.

    1. Login to your JIRA account using valid credentials
    2. Choose the Jira icon > Dashboards
    3. Click ••• and choose Create dashboard to create a blank dashboard. You can also choose Copy dashboard to create a copy of the dashboard you are currently viewing
    4. Create dashboard page is displayed
    5. Name your dashboard and add a description
    6. Fill out the remaining fields and click Create
      Note: Dashboard can be edited, copied, shared and deleted from the manage dashboard section

    40. How to add Gadgets to a dashboard in JIRA?


    You must be a JIRA admin to add a gadget to a dashboard in JIRA. Some applications allow dashboards that are shared by groups of people. If you have permission to update a shared dashboard, the other people sharing the dashboard will see your changes too.

    Following are the steps to add a gadget to a dashboard:

    1. Go to the dashboard by selecting the Dashboards link in the navigation bar.
    2. Click Add Gadget on the dashboard.
    3. Use the gadget wizard to pick the gadgets you want to add.

    41. What is a Kanban board in JIRA?


    A Kanban board in JIRA is a board that was created using either the Kanban preset or the DIY option. If a team’s focus is on managing and constraining their work-in-progress then Kanban board is suitable for them.

    42. What is a Scrum board in JIRA?


    A Scrum board in JIRA is a board that was created using the Scrum preset. If a team is planning to work in sprints then Scrum board is suitable for them.

    43. What is a validator in JIRA?


    Validators in JIRA check that any input made to the transition is valid before the transition is performed. The issue will not progress to the destination status of the transition when a validator fails.

    44. What is an issue collector?


    An issue collector in JIRA allows you to easily embed a JIRA feedback form into your own website. This helps website visitors to log issues into JIRA through your website. Visitors to your website do not require a user account in JIRA to use the JIRA feedback form.

    45. What is an Audit log?


    The audit log in JIRA allows administrators to look back at changes that have been made in your site. Audit log helps you in troubleshooting a problem

    Course Curriculum

    Get Practical Oriented JIRA Training to UPGRADE Your Knowledge & Skills

    • Instructor-led Sessions
    • Real-life Case Studies
    • Assignments
    Explore Curriculum

    46. Explain the JIRA workflow.


    Workflow defines the series of steps or stages an issue/ bug goes through during its lifecycle from creation to the closing of the issue.

    The workflow here includes the creation of an issue, a series of actions performed to fix the issue and the last step includes the closing or say completion of the issue after verification.

    Refer the below diagram for better understanding:


    47. Enlist the report types generated by JIRA.


    There are multiple reports available in JIRA which are used to show the project statistics throughout the project life cycle. There are general reports available for analyzing issues as well as different reports for Scrum projects and Kanban projects.

    General reports generated as and when required for analyzing issues includes:

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

    Examples of reports generated for Scrum projects are:

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

    Examples of reports generated for Kanban projects:

    • Control chart
    • Cumulative Flow diagram.

    For generating reports for your project, follow the below steps:

    • Navigate to the desired project dashboard.
    • Click on the Reports tab from the left-hand side to view different reports.
    • Click on Switch report to view the different reports.

    48.  Explain the step by step procedure of how an issue is created in JIRA.


    Whenever an issue or defect is encountered while testing, it needs to be reported so that the developers can work on it and take the necessary action to fix it.

    We will see step by step as how an issue is created in Atlassian JIRA.

    a) Log in to your JIRA account by using valid credentials and get directed to the dashboard.

    b) Click on the ‘Create’ button displayed and you will be navigated to a window for creating an issue.

    c) Enter all the necessary details as required to create an issue. The below field example can be understood better by the image below.

    • In the Project field, a project for which we are creating an issue is selected. In this example: STH_Learning(STIHL) is selected from the dropdown containing all the available projects.
    • In the Issue type field, the nature of the issue is selected from the dropdown which contains options like Bug, Task, Improvement, Story, New Feature, etc. In this example, ‘Bug’ is the nature of the issue.
    • The Summary field contains the one line title of the issue which imparts the critical information about the issue in a summarized way. The more effective the issue headline, the more you can show the criticality of the issue. Of course, the headline should be easily understood without any chances of misinterpretation. The example I have taken here, however, is not very critical.
    • The Reporter is the one who reports the issue. In most of the cases, the name of the Project Manager is selected in this field.
    • In the Description field, the detailed description of the issue is written. As you can see in the below example screenshot, Steps to reproduce the issue, Actual result, Expected result are included in the description.
    • In the Affect Version field, the current build version of the project is selected in which the issue has been encountered.
    • Fix version field is basically selected by the concerned developer people, who choose the version as and when their work for the particular issue has been finished and the issue has been fixed.
    • Priority field defines which issue should be considered first to be fixed. Tester selects the priority of the issue from the dropdown based on its effect on the application. This example issue is basically of a Medium priority.
    • In the Attachment field, any video or screenshot related to the issue is being uploaded.
    • In the Environment field, operating system and browser details are mentioned on which issue has been encountered.

    d) After all the details have been completed, click on the ‘Create’ button displayed on the window to create the new issue.

    e) The issue id is generated which can be used in the future as a reference for tracking the progress of the issue.

    49. Explain the three color indicators and their significance.

    Ans: For any particular issue in JIRA, 3 colors like Blue, Green, and Orange is used to denote the amount of time spent on any particular issue. This information is displayed under the ‘Time Tracking’ section. Each color has its own significance like;

    • Blue: This color is to denote the ‘Original Estimate’ i.e. the time estimate to be invested in resolving the issue. This field has been labeled as ‘Estimated’.
    • Orange: This color determines the time left for resolving the issue. This field has been labeled as ‘Remaining’.
    • Green: This color defines the actual time that has been used or say spent in resolving the issue so far. This field has been labeled as ‘logged’.

    50. For any particular issue, what all are included under change history?


    Change history section displays the activities of changing any records with information regarding the person who has made the change as well as the time at which the changes have been made.

    The change history also displays information about the old and new field values in the case of the change in any field.

    Change history includes the following records of the changes:

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

    Change history for any issue can be viewed in JIRA by following steps:

    • Open any particular issue.
    • Click on the ‘History’ tab present in the ‘Activity’ section.

    51. Mention a way with which an issue can be shared with other users in JIRA.


    An issue can be shared with other users in JIRA by using the share option available on the issue description page.


    When the share option for any particular issue is clicked, it contains the link to the issue to be shared along with ‘Username or Email’ and ‘Note’ field that has to be filled.


    52. What is the importance of labeling issues?


    Labeling an issue is basically done to categorize an issue within a particular section which in turn can be easily searched with the help of labels.

    Label for a particular issue can be initially set at the time of creating the issue, while it can edit also within the issue. Label field is displayed under the ‘Details’ section as shown below in the figure:


    53. What is the purpose of the JIRA dashboard?


    The first page which is displayed whenever we get logged in to JIRA application is ‘Dashboard’ which is basically the default or system dashboard.

    A personal dashboard can also be created and designed by adding different gadgets and can be edited also as and when required. These gadgets are the means to display the project progress in terms of issues, etc.

    Let us understand the steps as how a personal dashboard can be created:

    a) Enter valid credentials and get navigated to JIRA dashboard.

    b) Click on “…” displayed on the upper right-hand side and choose option ‘Create dashboard’. You can also choose ‘Copy dashboard’ in the case of copying the currently viewed dashboard.


    c) ‘Create Dashboard’ page is displayed.

    d) Enter all mandatory information and click on ‘Create’ button.


    e) After creating a dashboard, you get navigated to a page where there are multiple options to select and add gadgets to your dashboard.


    f) There is also an option available to choose and edit the layout of your dashboard.

    Any particular Dashboard can be edited, copied, shared, deleted from the Manage Dashboard section.

    54. What do you mean by Scheduling an issue?


    Scheduling the issue means scheduling the work of the issue for a particular ‘due date’.

    For this function to work, one must have ‘Schedule issue permission’ by JIRA Administrator. In this case, a field with ‘Due Date’ is being populated.

    55. Explain how particular project details are listed in JIRA.


    The project has some main attributes which have to be displayed in the project summary.

    This attributes include:

    • Name of the project
    • Key
    • Components
    • Versions (if present)

    Please refer below screenshot of Project ‘STH_L’ summary page as your reference. Although not much activity has been done in this project but this image will give you a clear idea.


    As you can see from the image, the middle display area of the page shows the ‘Activity’ screen containing details on the activities done on issues or project.

    The right-hand side section displays the basic information about the Project like Project Lead, Key, Issue Status, etc.

    The left-hand side contains various options like Components, issues, Reports, Active Sprints, etc. The related information is displayed as per the selection from the option.

    For Example: If I select the ‘Issue’ option, the below-displayed screen will appear.

    Jira Sample Resumes! Download & Edit, Get Noticed by Top Employers! Download

    56. What are issues types that are created and tracked via JIRA?


    JIRA has some defined set of default issue types which are displayed under the ‘Issue Type’ section.

    Other issue types can be added, edited and deleted as per requirement of the project. Some of the common issue types are Bug, Task, Sub-task, Epic, Story, etc.

    Their details can also be seen under the Issue type section as shown in the below figure.


    As the definition of ‘Issue Type Schema mentioned in JIRA application,

    An issue type scheme determines which issue types will be available to a set of projects. It also allows specifying the order in which the issue types are presented in the user interface.

    There are two types of Issue type Schema:

    • Default Issue type schema
    • Scrum Issue type schema

    57. Explain the term Cloning an issue.


    Cloning an issue means copying an issue.

    In this condition, a clone of the original issue is created which consists of the same information as is present for the original issue. Cloning of the issue is done so that multiple users can work on the same issue, however, the operation done either on the original issue or clone issue has no effect on each other.

    All the information of the original issue are cloned expect few as mentioned below:

    • Time tracking
    • Comments’
    • Issue history
    • Status and Resolution

    Let us see how to create a clone of an issue:

    a) Open any issue by searching with an issue id or create any new issue id.

    b) On the right-hand side of the issue description screen, you will see “…”. Click on it and options are displayed.

    c) Click on Clone from the displayed dropdown option.


    d) Clone Issue window is displayed.

    e) If required, you can edit the summary of the issue and click on the ‘Create’ button.


    f) Another issue is created with ‘CLONE’ added in the summary.

    58. Explain the Kanban board.


    Kanban boards are created for the projects where the team has their prime focus on visualizing the workflow and managing the project’s work in progress.

    The most important feature of Kanban board is that it is found in work mode because the projects do not have their work as planned.

    Let us see how the Kanban board is created in JIRA step by step.

    a) Log In to the JIRA application using valid credentials and get navigated to the dashboard.

    b) Click on Project dropdown and select the option ‘Create Project’.

    c) Select ‘Kanban Software development’ and click on the Next button.


    d) Enter all the necessary details and click on the Create button.

    e) Kanban board is created as shown in the below example.


    In the case of Kanban, the incoming task is given more priority and hence it is considered as the best methodology for cases like bug fixing and maintenance release.

    62. Mention one similarity and one difference between JIRA Scrum and JIRA Kanban.


    Similarity: Both JIRA Scrum and Kanban are considered as the most powerful process tool for optimization of work and the processes as both processes focus on continuous optimization and visualizing the workflow. In these cases, large and complex tasks are broken down and each individual task are worked on and completed efficiently.

    Difference: Scrum board is the work mode where progress of sprints and tracking of its work is done. Here the team determines the list of issues that have become backlog and then these issues are moved to sprints as per team plan.

    In the case of the Kanban board, the work in progress activities is being maintained and their process flow is tracked. Here the team decides the increase and decrease of the number of issues that is to be displayed in each status of the workflow.

    59. What are the most useful JIRA add-ons?


    Some of the most useful JIRA add-ons are listed below:

    • Jenkins-CI
    • Usersnap
    • Slack
    • HipChat
    • GitHub
    • PagerDuty
    • Tempo Timesheets

    60. What comes under JIRA Schema?


    JIRA Schema consists of the following:

    • Workflows
    • Issue types
    • Custom fields
    • Screens
    • Field configurations
    • Notifications
    • Permissions

    61. How is the security setting helpful in JIRA?


    The security setting for any issue is defined or set either at the time of the creation of the issue or while editing the issue.

    The basic reason for security settings is to restrict user access to the issue so that not all users are able to work on that issue. Security setting also allows the access of the issue to the member of chosen security level.

    Are you looking training with Right Jobs?

    Contact Us
    Get Training Quote for Free