JIRA Interview Questions

Get Technical Answers for JIRA Interview Questions by JIRA Developer Experts, Advanced Technical Questions for Freshers and Experience Persons. Get Free Practical Test

1. Explain What Is Jira?

Ans: JIRA is nothing but an issue tracking product or software testing tool developed by the company Atlassian. This tool is mostly used for the bug or issue tracking, managing the project, and debugging the complex errors.  JIRA tool usually runs on these three aspects and is widely used in software development projects.

2. Why JIRA is used?

Ans: Atlassian developed JIRA is nothing but an issue tracking tool and most commonly used in agile methodology. Let me explain the few advantages of using JIRA;

  • JIRA is a platform-independent tool and that can run on any operating systems
  • JIRA workflows are easy to customize completely based on user requirements.
  • Cost-effective and user-friendly software testing tool
  • Using the JIRA tool user can easily debug the complex errors
  • JIRA software tool allows user to track the progress of a project on time to time base

3. Explain the JIRA workflow?

Ans: JIRA workflow is a set of software-related activities that are used to perform operations like tracking an issue and transitions during the software development life cycle. The transition is a link between the two statues and the issue moves from one transition status to another status. The status defines the nature of the work which is done by the tester.

The following are the important phases that occur in the JIRA workflow;

  1. Todo List
  2. In progress status
  3. Finally done.

4. What are the important differences between JIRA and Bugzilla?

Ans: Let me explain a few important differences between JIRA and Bugzilla

Bugzilla

JIRA
Bugzilla is an open-source software tool Whereas JIRA is a commercial software tool
Bugzilla is not a user-friendly tool Whereas JIRA is a user-friendly software tool
Drag and drop issue options are not available in Bugzilla Drag and drop issue options are available in JIRA
Bugzilla has only one configuration link type JIRA has a configuration link types which contains user-defined semantics
Supports blocks/user depends on the custom option available JIRA has a pluggable debugging links and user can access them outside of the tool
Bugzilla owns show/hide the customized common field or specific values JIRA software tool allows customized configuration based on the project type and type fields

5. Is it possible to access the JIRA cloud site via a mobile device?

Ans: The answer is yes, the user can access the JIRA cloud site via a mobile device, for that you have to use the appropriate URL of the JIRA mobile cloud site in your mobile website browser.

6. Can JIRA be used for test case management?

Ans: As we know, the JIRA architecture was not designed to work well with the server as a test case management tool. So it will be configured to support the test case management system in two different possible ways. After that users can either change the native JIRA components to meet the test case management system and also you can use add-ons option available in the parent company (Atlassian marketplace).

7. Explain labeling and linking issues in JIRA?

Ans: 

Labeling issue: This issue enables the user to categorize the raised issue in the form of information and later it is assigned to any component or version. This issue can be found using labels.

Linking issue: this issue enables the user to link any kind of issue or multiple issues that can also be associated either on the same or different JIRA servers.

8. List the types of reports generated in JIRA?

Ans: JIRA generates the reports which are based on the project, version, or any fields within the given issues. Let me give a few examples,

  1. Pie chart report
  2. Resolution time report
  3. Average Age report
  4. Recently created issue report
  5. Resolved versus created issue report
  6. Single level group report
  7. Project time tracking report
  8. User-defined workload report
  9. Pie chart workload report

9. What is cloning an issue in JIRA?

Ans: The cloning issue in JIRA allows users to generate a duplicate of the original issue so this makes the developer work on a single issue within a single project. The clone issue in JIRA can be connected to the original issue, and holds information like,

  • Summary details
  • Description details
  • Assignee
  • Work environment info
  • Issue type
  • Security info
  • Priority detail
  • Reporter and component detail.

10. How does a service desk work in JIRA?

Ans: This explains how the customer and service desk agent can work together to resolve the issue. First, the customer submits a request -> a portal or by mail service desk agent, user can see the request in the JIRA request service desk line, and later they perform an investigation. The customer and other user participants make use of the portal or email to discuss the issue and the person (service agent) who resolves the issue. Finally, the service agent completes the request and the customer is satisfied.

11. How are reports generated in JIRA?

Ans: The following steps explain how to generate a report in JIRA,

Step 1: first navigate to the desired JIRA dashboard -> click on reports -> now you can find different types of reports

Step 2: Now click on Switch report -> now you can view a different report

Step 3: now click on the report to see other options for reports.

12. What is an issue in JIRA?

Ans: An issue in JIRA represents anything in the form of a software bug, project-related task, or any request form. Issues are considered as the building blocks of JIRA software projects. The different organization uses the JIRA to track the issues which are raised during the development of a software project.

13. Explain how an issue is created in JIRA?

Ans: Let me explain the steps involved to create the issues in JIRA;

Step 1: Click on the create a button on the top of the screen-> this opens the create issue dialog box.

Step 2: Now select the relevant project and issue type -> this option available in the create issue dialog box.

Step 3: type the summary ->complete any appropriate fields

Step 4: make sure that you have checked all the fields correctly before creating the next issue in the dashboard.

Step 5: if all the details are valid-> now click the create button.

14. What are the color indicators in JIRA and mention their significances?

Ans: There are 3 primary color indicators available in JIRA such as;

  •       Blue color -> this color denotes the original estimate time.
  •       Orange color -> this color denotes the remaining estimate time.
  •       Green color -> green color denotes the time spent or logged details.

Jira Training Certification

  • Master Your Craft
  • Lifetime LMS & Faculty Access
  • 24/7 online expert support
  • Real-world & Project Based Learning

 

15. What is a Kanban board in JIRA?

Ans: A Kanban board in JIRA is nothing but a board that can be created using either Kanban preset or the DIY options. This Kanban board is suitable for those whose focus is on only managing and constraining work-in-progress time.

16. What is a SCRUM board in JIRA?

Ans: A scrum board is nothing but a board that is created using the Scrum preset option. This Scrum board is suitable for those who have planning to work in Sprints time.

17. How to create a burndown and burn up charts in JIRA?

Ans: 

Burn up chart creation steps:

  1. Go to the JIRA official web page.
  2. Now click on the project that you are working on.
  3. Click on the reports -> appears at the left side
  4. Now it’s time to select the Burn-up chart option.

Burndown chart creation steps:

  1. Go to the JIRA official web page.
  2. Now click on the project that you are working on.
  3. Click on the reports ->appears on the left side of the panel.
  4. Now select the burn down from the reports drop-down option.

18. Define the components used in JIRA?

Ans: Jira components are nothing but the subdivision of a project which is used to group the issues within a software project into smaller ones.

19. Define the validator in JIRA?

Ans: The validator in JIRA checks the input which is valid in transition level and it will not progress any kind of issue to the destination transition status when it fails.

20. How is the security setting helpful in JIRA?

Ans: JIRA security setting is used to restrict any access to the issue to only those who have authorized to work on issues. This security level of any issue can be set either when the issue is created or when it is being edited.

21. How can you modify multiple bulk issues?

Ans: To modify any bulk issue, you need to use the bulk change options -> tool menu-> now select all the issues on the current page that can be now used for the bulk operations.

The following details you will get when you perform a bulk operation such as;

  • Workflow transition
  • Delete
  • Move
  • Edit

22. What are some of the popular add–on for JIRA?

Ans: Some popular add –on for JIRA included are,

  • Suites the utilities for JIRA
  • Script Runner
  • Zephyr for JIRA
  • JIRA toolkits
  • REST API browser
  • JIRA portfolio
  • MISC workflow extensions
  • Tempo timesheets
  • Chart plugins

23. Define schemas in JIRA?

Ans: Schemas are one of the major parts of JIRA configuration systems. These collected configured values were later used by one or more JIRA projects. The examples are notification schemas, issue type schema, permission schema, and many more.

24. In JIRA workflow, is it possible to transition an issue back to its previous status?

Ans: Practically speaking, this is not possible to transition an issue back to its previous status. However, for an emergency purpose, you can use the “On hold “feature to perform this task.

25. For any agile project, how user stories in JIRA are created?

Ans: The following steps will explain how to create user stories in JIRA;

  • Issue type – epic and issue types ->then the agile stories linked to it. To perform this follow the navigation “create issue “page -> then go to the “configure fields” -> select the “epic link”.
  • Or the user can have a product backlog feature -> by creating the main user story -> create sub-tasks under it.

26. What is the JIRA dashboard?

Ans: JIRA dashboard is a type of web browser page that includes many user-friendly tools and features to work on any kind of issue.

27. What is the use of move issue wizard in JIRA?

Ans: The move issue wizard helps users to specify the JIRA project in any JIRA instances. This issue permits users to perform any type of modification to certain attributes of the issue such as issue status, and custom field values.

28. What is an audit log?

Ans: Under the Audit log in JIRA, the user can see all the details about the issues generated, and also changes made to any issue.

29. How to add your gadgets in the JIRA dashboard?

Ans: The following navigation explains how to perform this,

First, go to the JIRA dashboard -> select the dashboard link -> click the “Add gadgets” button on the dashboard -> now use the gadget wizard to pick the selected gadgets.

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

Ans: If the JIRA workflow is active, the user cannot edit the workflow name and description.

  •       User cannot able to delete the workflow steps
  •       A steps involved in status cannot be edited.
  •       A step ID cannot be changed or edited.

31. Why Use Jira?

Ans: The reason behind using JIRA is

  • Upfront and fair licensing policy
  • Features that is not available elsewhere
  • Get latest update on the progress of projects
  • It run anywhere and recognized with many famous companies
  • Easily extensible and customizable

32. Explain Labelling And Linking Issue In Jira?

Ans: 

Labelling Issue: It enables you to categorize an issue in a more informal way than assigning it to a component or version. You can then search issues according to label.
Linking Issue: This feature enables you to link an association between two issues on either on the same or different JIRA servers.

Subscribe to our youtube channel to get new updates..!

 

33. Explain How You Can Share An Issue With Other Users?

Ans: You can email an issue by using the share option in JIRA. You can also email other JIRA users a link to the issue by sharing the issue with them or by mentioning them in an issue’s Description or Comment field.

34. Explain How You Can Disable Mail Notification For Bulk Operations?

Ans: To disable mail notification for a particular Bulk Operations, you have to de-select the “Send Notification” checkbox in the bulk operation wizard.

35. What Does An Issue Change History Include?

Ans: 

  • Issue change history includes
  • Deletion of a comment
  • Deletion of a worklog
  • Creation or deletion of an issue link
  • Attachment of a file
  • Changes to an issue field

36. Explain What Does The Three Color Indicates Tracking Times Or Duration For An Issue?

Ans: Three color will be displayed representing the amount of time spent behind the issue:

Original Estimate (Blue): The amount of time originally estimated to resolve the issue

Remaining Estimate(Orange): The remaining amount of time left to resolve the issue

Time Spen or Logged (Green): The amount of time spent so far while resolving the issue

Jira Training Certification

Weekday / Weekend Batches

 

37. Mention Some Of The Popular Add-ons For Jira?

Ans: Some popular add-ons for JIRA include,

  • Suites utilities for JIRA
  • ScriptRunner for JIRA
  • Zephyr for JIRA – Test Management
  • JIRA Toolkit Plugin
  • Atlassian REST API Browser
  • Portfolio for JIRA
  • JIRA Misc Workflow Extensions
  • Tempo Timesheets for JIRA
  • JIRA Charting Plugin

38. Mention What Is Schemes In Jira?

Ans: Schemes are a major part of JIRA configuration. It is a collection of configured values that can be used by one or more JIRA project. For instance, Notification Schemes, Permission Scheme, Issue Type Scheme, and so on. There are total seven types of schemes.

39. Mention Is It Possible To Get Back Up Your Jira Cloud Data?

Ans: In JIRA, you can take backup of your JIRA cloud data using Backup Manager. But only one backup file is stored at a time. The existing backup is overwritten by new ones.

40. Mention What Data Can Be Backed Up?

Ans: The backup data includes:

  • Attachments if selected
  • Users and their group settings
  • Avatars
  • Issues

41. Mention Some Useful Tips On Jira Workflow?

Ans: As such Statuses are global objects in JIRA. Changing the name of the status on one workflow will change the status on all workflows that use that status

  • Hover over a status or transition to see the relevant transition labels
  • One cannot clone transitions in the workflow designer
  • In the workflow designer, one cannot create annotations
  • Directly you cannot set the issue.editable property.

42. Mention What Is The Role Of Validators In Jira?

Ans: The Validators in JIRA checks that any input made to the transition is valid before the transition is performed. If a validator fails, the issue will not progress to the destination status of the transition

43. What Is An Event In Jira?

Ans: The events are classified in two a System event (JIRA defined events) and Custom event (User defined events). An event describes the status, the default template and the notification scheme and workflow transition post function associations for the event.

Submit an interview question

Categories

Request for more information

Sachin
Sachin
Networking, OS, Salesforce & Sap
Am sachin I have worked with hkr trainings for more than 4 years .and our methodologies had been a practical suit for student culture and professionals. And I have trained more than 30 batches over the last 8 months. And I have great experience working with hkr trainings. Contact me with my LinkedIn and Twitter.

WhatsApp
To Top