JIRA Interview Questions

1. What Is Jira?

Ans. JIRA is a popular software testing tool and an issue-tracking product from Atlassian, an Australian IT company. It is also a famous bug-tracking tool that tracks various issues in project management. This tool is popularly used in software development and testing projects. Also, JIRA covers multiple reporting tools that help manage projects related to development and track many potential bugs and software errors. 

Become a master of Jira by going through this HKR Jira Course!

[ Related Article: Jira Course ]

2. Why JIRA is used?

Ans. JIRA is popularly known as a software testing, issue tracking, and project management tool. JIRA can be used for different purposes in software development and project tracking. Here are some benefits of using the JIRA tool:

• It helps in tracking the progress of various IT projects. 
• This tool is platform-independent.
• Jira can run on different Operating Systems with compatibility. 
• It is easy to customize the platform as per user needs.
• Further, it is a very user-friendly and cost-efficient tool.
• It also helps to automate various workflows.

3. Explain the JIRA workflow?

Ans. JIRA workflow is a group of various software activities helpful in tracking the different transitions of a bug or issue in the SDLC process. Transitions connect the two statuses when an issue transits from one status to another. Hence, the status mentions the nature of work performed by the tester. However, the three essential stages of JIRA workflow are as follows:

• Open/Started
• Work in Progress
• Close/Finally done.

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

Ans. The following are the key differences between JIRA and Bugzilla:

• JIRA is a popular commercial tool, whereas Bugzilla is an open-source tool.
• Bugzilla is mainly a bug-tracking tool, but JIRA is a complete project management and issue-tracking tool. 
• JIRA is a highly intuitive and user-friendly tool, but Bugzilla needs a more interactive UI.
• JIRA can be easily customizable per various business needs, but Bugzilla has limitations. 
• Bugzilla cannot integrate with other tools seamlessly, whereas JIRA can easily integrate with other Atlassian tools.
• JIRA has no advanced search options feature, but Bugzilla has such an option. 

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

Ans. Yes, using the JIRA cloud site URL, you can access the JIRA cloud site through your mobile's web browser.

6. Can JIRA be used for test case management?

Ans. As far as we know, the server's test case management functionality was not well-integrated into the JIRA architecture. The test case management system will be set up in two alternative ways to support the test case management system. After that, customers have the following two options: they may either modify the built-in JIRA components to conform to the requirements of the test case management system, or they can utilize the add-ons that the parent business offers.

7. Explain labeling and linking issues in JIRA?

Ans.

• Labeling issue: 

Labeling is also known as "tagging," which allows you to categorize an issue as information that can be allocated to any component later. You can find this issue through labels. 

• Linking issue: 

You can use this functionality to establish a relationship between two issues on separate or identical JIRA servers.

8. List the types of reports generated in JIRA?

Ans. JIRA produces the following reports on the issues based on versions, projects, etc. Here are a few examples of the various reports:

• Pie Chart Report
• Average Age Report
• Resolution Time Report
• Recently created issue report
• User-defined Workload report
• Pie-chart workload report
• Created issue Vs. Resolved issue report
• Project Time-Tracking report
• Single-level group report

9. What is cloning an issue in JIRA?

Ans. In JIRA, cloning an issue enables users to produce a copy of the actual/original issue. It allows multiple teams or developers to work on a single issue. Further, a clone issue can also be connected to the actual issue, containing the following information. 

• Summary details
• Assignee
• Work environment info
• Security info
• Description Details
• Issue type
• Reporter 
• Priority 
• Component detail

10. How does a service desk work in JIRA?

Ans. A service desk plays a key role in a company's IT infrastructure and is a central point of contact. A service desk agent works to address customer issues, inquiries, and technical support requirements. The service desk aims to provide seamless delivery of various IT services, improve efficiency, and increase user satisfaction.

The process typically starts with a request submission by a user through a web portal, email, or phone call. In the JIRA service desk line, they find the request sent and start action against it. Further, the service desks also follow IT best practices to resolve customer queries. Thus, they complete the customer requests and make them satisfied. 

If you want to Explore more about Jira? then read our updated article - Jira Tutorial

Jira Training Certification

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

Explore Curriculum

11. How are reports generated in JIRA?

Ans. The below-listed steps how to produce a report in JIRA:

• Select the desired JIRA dashboard -> click reports -> a variety of report kinds are now available.
• Go to "Switch report" to view an alternative report.
• To view other report options, click on the report.

12. What is an issue in JIRA?

Ans. In JIRA, an issue refers to anything that is a software bug or a task related to a project. For the JIRA software projects, issues are the primary building blocks. However, multiple companies use JIRA to track issues occurring during the software development project. 

13. Explain how an issue is created in JIRA?

Ans. The following is the process to follow during the creation of an issue within JIRA:

• To open the "create issue" dialog box, hit the "create" button at the top of the screen.
• Next, choose the relevant project and issue category from the "Create Issue" box options list.
• Type the "Summary" and fill in the appropriate fields. 
• Before producing the subsequent issue on the dashboard, confirm that you have correctly filled out all the fields.
• Click the "Create" button if all the information is correct.

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

Ans. In JIRA, the following are the primary color indicators:

• Blue color: The blue color indicates the actual evaluated time.
• Green color: The time spent or logging details are indicated by this color.

Orange color: This color indicates the balance estimated time.

15. What is a Kanban board in JIRA?

Ans: JIRA Kanban board  refers to the board built through DIY options or using the Kanban preset. Moreover, this board is perfect for people only interested in managing and restricting their ongoing work time.

16. What is a SCRUM board in JIRA?

Ans. In JIRA, the Scrum board is most useful for IT teams who want to work in Sprints or phases. 

Further, this board aids in bringing all the teams together to work toward a single goal. Moreover, Scrum is quite helpful in the software development process.

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

Ans: 

Steps for creating a Burn Up chart:

• Visit the official JIRA website.
• Click on the project you are currently working on.
• Select the reports icon, which will display on the left.
• The Burn-up chart option needs to be chosen here.

Steps for creating a Burndown chart:

• Visit the official JIRA website.
• Click on the project you are currently working on.
• Select the reports icon that displays on the panel's left side.
• Now, choose the burndown option from the drop-down menu of reports.

18. Define the components used in JIRA?

Ans. The components in JIRA are simply project divisions used to divide software project issues into more manageable chunks.

19. Define the validator in JIRA?

Ans. Before the transition runs in JIRA, the validator verifies that the input provided to the transition, whether the transition is valid. Moreover, the issue won't progress to the target state of change if the validator fails.

Become a master of Jira by going through this HKR Jira Training!

20. How is the security setting helpful in JIRA?

Ans. By using the JIRA security setting, only those individuals who have been granted permission to work on issues can access the issue. Every issue's security level can be adjusted during creation or change.

21. How can you modify multiple bulk issues?

Ans. Use the bulk change choices -> tool menu -> choose all the issues on the current page that can now be used for the bulk activities to alter any bulk issue.

You will receive the following information when you carry out a bulk operation, for example:

• Workflow change 
• Remove
• Move
• Modify

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

• Ans. 

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

23. Define schemas in JIRA?

Ans. In JIRA configuration systems, Schemes are essential components. However, these are a group of configured settings that one or more Jira projects may use in the future. Further, there are seven different kinds of schemas: issue type schemes, permission schemas, and notification schemas. 

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

Ans. A problem cannot be changed back to its original state. However, you can complete this task using the "On hold" option in an emergency.

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

Ans. The steps below will walk you through creating user stories in JIRA: issue type -> epic and types of issues -> then the related agile stories. To do this, navigate to the "create issue" page, click the "configure fields," and then move to "epic link."

Alternatively, the user can build subtasks under the main user story by creating a product backlog feature.

26. What is the JIRA dashboard?

Ans: JIRA dashboard is an online website with various tools and features. They are easy to use while working on any issue.

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

Ans. Users can specify the JIRA project through the move issue wizard in JIRA. Hence, it allows users to alter any aspect of the issue along with the issue status and the custom field values.

28. What is an audit log?

Ans. In JIRA, a user can view all the information on the issues produced and their changes in the audit log.

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

Ans. You can follow these steps to add gadgets to the JIRA dashboard:

First, move to the JIRA dashboard and hit the dashboard link. Then, click on the "Add gadgets" option. Next, choose the gadgets you want to add through the gadget wizard.

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

Ans. Users cannot alter the workflow name and description in an active JIRA workflow.

• The user cannot remove workflow steps.
• It is impossible to alter the status-related stages.
• It is impossible to edit or modify a step ID.

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?

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

Ans. You can email an issue to others by using JIRA's share feature to share it. Additionally, you can email other JIRA users a link to the problem or include a note of it in the issue's Comment or Description section.

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

Ans. To turn off mail notifications for a specific bulk activity, you must deselect the "Send Notification" button in the bulk operation wizard.

35. What Does An Issue Change History Include?

Ans. The history of issue changes comprises the following:

• Removal of a comment
• removing a work log
• Building or removing an issue link
• An attached file
• Modifications to a field of issue

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

Ans. Three colors will be shown to indicate how long the issue has been ongoing:

• Actual Estimate (Blue): The time initially projected to address the problem
• Remaining Estimate (Orange): The amount of time needed to finish the problem
• Time Spent or Logged (Green): The total time invested in fixing the issue so far.

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. A key part of JIRA configuration is the schemes. One or more JIRA projects may use these schemes as the group of set-up values. Notification schemes, permission schemes, and issue-type schemes are a few examples. Further, there are seven different kinds of schemes.

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

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

Ans. You can use the Backup Manager in JIRA to back up your cloud data. However, only one backup file is kept on file at once. New backup files replace the old ones.

40. Mention What Data Can Be Backed Up?

Ans. The following data can be backed up in Jira:

• Attached files if selected
• Users and their group settings
• Issues & Avatars

41. Mention Some Useful Tips On Jira Workflow?

Ans. In JIRA, statuses are the global objects. Any workflow that uses a certain status will have its status changed if its name is altered.

• To view the appropriate transition labels, hover over a status or transition.
• In the workflow designer, transitions cannot be copied.
• It is not possible to make annotations inside the workflow designer.
• You cannot instantly fix the property issue.editable.

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

Ans. Validators play a great role in JIRA software. They check the various inputs used in the transition are valid or not before the execution of transition. In case of failure, there will be no further progress in the issue to transition's target status.

43. What Is An Event In Jira?

Ans. An event contains information about its state, default template, notification system, workflow transition, and event's post-function interactions. In JIRA, the events can be divided into System Events and Custom Events. These are JIRA-defined and user-defined events, respectively.

44. What issues can we not clone in JIRA?

Ans. The following issues can't be cloned in Jira such as time tracking, comments, and history of an issue.

45. Define JQL.

Ans. JQL refers to JIRA Query Language, which provides many advanced and adaptable methods for identifying a wide range of JIRA issues. Field, operator, keyword, and value are all included in JQL. This language is helpful for developers, managers, testers, business users, etc. 

46. What is meant by JIRA Core?

Ans. An application called JIRA Core provides an adaptable workflow management solution. By offering a framework for automating numerous business processes, it facilitates a company of different tasks and projects into a single, central location. As a result, it increases the team's total productivity.

47. What elements make up a JIRA Schema?

Ans: JIRA Schema includes the following elements:-

• Issue Types
• Notifications
• Screens
• Permissions
• Field Configuration
• Workflows

48. What is meant by Issue Collector?

Ans. Users can use the issue collector to integrate a JIRA feedback form into their website. Generally, a user can open a form by clicking on a trigger tab in the margin of the website's webpage.

49. Name the Agile methodologies that support JIRA.

Ans. The following Agile methodologies support JIRA: Kanban and Scrum.

50. List the various Issue types in a Scrum project within JIRA.

Ans. The Scrum project in JIRA comes with the following issue forms by default: 

• Epic 
• Story 
• Task 
• Bug

51. Name the various source control tools that JIRA integrates.

Ans. The different source control applications that are simple to combine with JIRA include the following:-

• Helix Core
• Subversions
• Git 
• ClearCase 
• Mercurial

52. How can you schedule an issue in JIRA?

Ans. We can quickly set up issue due dates within JIRA, which makes it easier to monitor, assess, and alert the team about the due date. The fantastic feature of issue scheduling is that it does a secure and comparable date search based on due dates. As a result, scheduling an issue within JIRA with the date field is simple. We can modify the current issue type or create a new one to do this.

53. Name the Post Functions performed after the execution of the transition.

Ans. The following post functions executed after the transition's execution:

• Updates to the issue field
• Adding a remark to an issue
• Creating events to initiate email notifications
• Modify the production history of an issue.

50. Mention the ways to ensure data security and privacy in JIRA.

Ans. Any company using JIRA software should prioritize privacy and data security. The following are the security best practices to use in JIRA:

• Using a firewall.
• Using a two-factor validation system.
• Using data encryption.
• Updating JIRA software.
• Taking data backup.

Conclusion

After going through these JIRA interview questions and answers, you can feel more confident attending the interview. These questions are compiled with the help of experts in the industry so that you can easily ace the interview of a QA Tester.