48 Jira Interview Questions & Answers That'll Get You Hired

Jira Interview Questions Answers

Jira is on the most popular agile software development tools for tracking work. It allows executives, managers, engineers, and designers to collaborate on features by using user stories, epics and release planning. All of which can be broken up into small pieces, divided between team members and made into active work. This active work is usually planned out into sprints, which consists of two-week intervals which contain certain goals the team is trying to meet. Jira is a large part of this planning effort as it allows all team members to see when certain user stories have been completed. It is by far one of the most popular agile software development tools for larger organizations, while smaller organizations might use competitive tools like Trello. Jira has a tendency to support larger organizations because of its level of detail and overall interface to the epics, stories, and assignments. These Jira interview questions and answers should help you get a jump start on the software and firmly understand its importance. That way when a hiring manager asks you about Jira and your understanding of it, you can answer. You might be applying for a management position, in which case, I would expect questions outside of Jira’s lens. As with all of the answers to these JIRA interview questions, they are mostly mock, yet factual. Meaning, please use this as a study guide but do not answer in your interviews with these answers verbatim. It will come off with a lack of confidence that’s required to make a strong impression.

1. Provide a definition of JIRA.

JIRA refers to a project management tool developed by Atlassian, Incorporated that allows for bug tracking and project management. It is a truncation of the word Gojira, which is the Japanese term for the monster, Godzilla and a reference to its competitor, Bugzilla.

2. Why is JIRA used?

JIRA functions as an issue tracking and agile project management tool that allows users to track any project through monitoring a proper workflow. Some of the benefits include the following.

• It can be run anywhere.
• It is platform independent.
• In JIRA, the workflow may be customized according to the set requirements.
• Aside from issue tracking, history of the work done on issues, when and by whom, can be tracked.

3. Explain the definition of a workflow in JIRA.

The workflow is a movement of the issue through different phases within the duration of the life cycle. This includes the creation of the issue/ bug, the sequence of actions done in order to solve the problem and the completion of the issue after verification takes place.

4. What is a workflow designer in JIRA?

The workflow designer in JIRA refers to a graphical tool, which allows a person to see the layout of the workflow and to initiate and modify the procedures and transitions of the workflow.

• It is possible to manage the status and transitions through adding, clicking or dragging to edit properties in order to rename or delete.
• One can add a global transition to the selected status. Therefore, you select the option to allow all of the Statuses to transition to this one within the properties board for the transition.
• One can customize the advanced transition options like the triggers, post functions, and other validators.
• One can change the screen, which the transition utilizes.

5. How does the service desk work?

• The customer remits a request to the service agents via the portal or by using their email
• Service desk agents view the request on their JIRA service desk line and look into the problem.
• The customer along with the other participants uses the email or portal to talk about the request with the service desk agent at the Service Desk.
• The service agent completes the request to the satisfaction of the customer.

6. How are reports generated within JIRA?

• Phase 1: go to the desired board and then click on the tab named ‘Reports’. There will be different forms.
• Phase 2: Click Switch report in order to view a different report.
• Phase 3: click on the switch report tab in order to see the different report.

7. What are the differences between JIRA and its competitor, Bugzilla?

• Bugzilla and JIRA are the prominent bug/ issue tracking tools, which are in use by a number of organizations. However, JIRA has been reviewed as user-friendly, while Bugzilla has been termed as complex.
• JIRA has configurable link types with user-defined semantics. It has pluggable remote issue links allowing the links to other entities outside of JIRA. Bugzilla though has one link mode that is blocks and a Bug ID custom type field.
• Bugzilla can allow the users to select the initial status of a new problem/ bug. JIRA though provides for the definition of several workflows that can be applied according to the Project and Type of the issue.
• JIRA does not have an advanced level search option. It has flexible JQL language known as the query language allowing the user to construct arbitrary Boolean expressions. Bugzilla has a powerful advanced search option.

8. Explain the process of how an Issue is created within JIRA.

When a problem is detected during testing, it needs to be reported to the developers are able to work on and take the needed steps to fix the problem. The steps for dealing with the issue are explained below.

• Log in to the JIRA account by utilizing valid credentials and proceed to the dashboard.
• Click on the ‘Create’ button displayed so that you navigate to the window for creating an issue.
• Enter the needed credentials as needed for the creation of an issue. • Locate the Project field for which you are creating an issue. In a particular example: STH_Learning ( STHL) would be selected from the dropdown with the available projects.
• Locate the Issue Type field and select its nature from the menu, which has options including the TASK, Bug, Improvement or New Feature. Here, you would input ‘Bug’ as the issue.
• The Summary field is next and has the one line title of the problem, which gives the significant information on the issue in a summary. The more concise and relevant the issue headline, the more you can show the critical nature of the problem. It needs to be simple without leaving a chance for misinterpretation.
• The Reporter is the field that reports the issue. The name of the project manager would be selected.
• Within the description field, you are to give the details on the bug. This includes steps to reproduce the issue and the result. The expected results need to be included within the description as well.
• In the affect version field, the current build version, a project would be selected in which the issue is encountered.
• Fix version field is next and selected by the developers that choose the version when the work for the issue is done and the issue is completed.
• The priority field concerns the issue that ought to be considered as the first to be fixed. The tester considers the priority of the problem from the menu according to its effect on the application.
• The attachment field allows for videos or screenshots related to the problem to be uploaded.
• Within the environment field, the operating system and other browser details are given on which issue has been encountered.
• After completing all of the details, you may click the ‘Create’ tab illustrated on the window in order to create the issue.
• The issue id is generated and this would be used in the future for tracking the progression of the bug.

9. How do you delete a component in JIRA?

On the ‘Components’ screen, go over the significant component so that the delete option is illustrated. You will be encouraged to connect these issues with another component.

10. Can JIRA be used for test case management?

Even though JIRA was not prescribed to serve as Test Case Management, it may be custom configured so that it does support it in two different ways. Either it is possible to change native components in JIRA to meet the needs of test case management for the individual or it may be possible to use one of the add-ons available within the Atlassian platform.

11. Is it possible to access the JIRA cloud site from a mobile device?

You can access JIRA cloud site from a mobile platform. You just have to utilize the URL of the cloud site within the mobile browser.

12. Is it possible to disable JIRA mobile for the site?

It is possible to disable JIRA mobile for the site and so users would not be able to operate the desktop of JIRA on their mobile device. JIRA mobile is a system add-on and would be disabled at any such time.

13. What are linking and labeling issues in JIRA?

• Linking issue: this would allow you to link associations between two issues on similar or different JIRA servers.
• Labeling issue: this would allow you to group an issue in an informal manner than assigning it to components or versions. You may search the issues according to the label. 14. How is the security setting helpful in JIRA? The security setting in JIRA provides a restriction for the access to the issue to only the individual allowed to be working on it or a person that passes a particular security clearance. Security levels of the issue can be customized when the issue is created or when it is being edited.

15. How is an issue shared in JIRA with other end users?

There is a share option available on the issue description page. The issue may be shared with others using the share option. Once you click on it, it will require you to give the username or email and possible, note to the recipient.

16. What are the color indicators in JIRA and what is their significance?

The indicators include blue, green and orange. Issue tracking is made easier through color-coding. They represent the amount of time, which is given to particular issues.

• Blue shows the initial estimation of time to resolve the bug.
• Green shows the time, which is spent or logged to solve the bug.
• Orange shows the remaining time, which is needed to resolve the issue.

17. Which elements are included when it comes to changing history?

• Creation and deletion of an issue linkage
• Creation and deletion of comments
• Attachment of files
• Issue field changes
• Attachment of files

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

Wizard allows you to specify another project within JIRA. The Move wizard allows changes of particular characteristics of the issue like the ISSUE Status, Custom Fields and the Issue Status.

• Issue Status: if you have given a particular status to the issue and it does not exist within the target project, then you have to select new issue statuses for the issue.
• Issue Type: If the issue is a custom issue type, which does not exist in the target project, then you have to select a new issue type.
• Custom Field: If you have defined the needed custom fields for your issue, which does not exist, in your target project, you have to set values for them.

19. How the project details are listed within JIRA?

The projects have a few attributes illustrate under the project summary designation. The list for the attributes in JIRA would include the;

• Nature of the project
• Keys
• Component
• Version

20. Describe the issue types in JIRA.

Each application has default issue forms. It is possible to use the default issue forms or create your own in order to suit the needs of the projects and the teams. Some of the core default types in JIRA include:

• Task- tasks, which need to be completed
• Subtasks- smaller tasks within the tasks The default issue types include: • Bug- a problem which impairs the functionality of a service or product
• Epic- a large amount of work which covers a number of issues
• Story- functionality requests which are considered from the perspective of the user
The Service Desk Default Issue types
• Incident- system incidents or outages
• Service requests- general requests from the user on services or products
• Change- the rollout of new solutions or technologies
• Problem- tracking some of the underlying causes of incidents

21. What is cloning an issue in JIRA?

The act of cloning or copying an issue allows you to create a duplicate within the same project. The cloned issue is the same as the original one and has the same information stored within the original issue such as the components and summary. The clone issue can also be linked to the initial one. It is a different entity from the first issue. Tasks of the original issue do not have an effect on the cloned issue and this goes both ways.

22. How to add Gadgets to the dashboard within JIRA.

It is a requirement to be a JIRA admin in order to add a gadget to the dashboard. Some of the applications allow for the dashboards, which are shared by different people. If you have permission to update a shared one the other people, sharing the dashboard will have access to the changes as well.

23. What is Zephyr for JIRA?

Zephyr refers to an add-on application, which gives very sophisticated test management allowances within JIRA.

24. What is the importance of the JIRA dashboard?

How would you create a new dashboard or customize the current dashboard within JIRA? The dashboard is the first page that one sees upon logging into the JIRA application. It is one of the default dashboards, which are the same for all JIRA users, but it is possible to come up with your own as per what you need. You can also design the dashboard through additions of gadgets. The following shows the phases of creating a dashboard within JIRA.

• Login to the JIRA account with the right credentials
• Select the Dashboard icon.
• Click on the three sequential dots and select the tab, ‘Create Dashboard’ to create a blank dashboard. You may also choose to copy the dashboard in order to create a copy of it you are currently viewing
• Create the dashboard page is illustrated
• Name the dashboard and add descriptions
• State the remaining fields and select Create. The dashboard may be edited, shared, copied and deleted if you go to the manage dashboard section.

25. When you log an issue or defect with the use of JIRA, which fields do you see?

When you log a defect, you see the Defect ID, the summary that is the short description, Description as the detailed issue, the identity of the person that detected it, the severity, date, priority, project, status and where it is assigned. Select the link to see the fields when you give a report on the defects within JIRA.

26. Give the source control programs with which it integrates.

It can integrate with a number of control programs like Subversion, Clear-case, Visual, Mercurial and Perforce.

27. Give an explanation on the manner you can modify multiple bulk problems.

In order to customize multiple bulk problems, it is possible to use the Bulk Change option from the ‘Tools’ menu of the navigator. All of the issues on the current page may be selected for the bulk operation. The detail list shows the available bulk operations which include

• Low transition
• Work
• Delete
• Move
• Edit

28. How is the subtask created in JIRA?

The subtask is a means of splitting the original problem into several smaller problems that are worked on individually. The initial problem has the information pertaining to the subtasks, which can be from the same project. The initial problem cannot be closed unless and until the subtasks have been concluded. The subtask has similar fields as the ones from any standard issue though the issue types seem to differ. The following is an illustration of the way the subtask is formed. It is an example to help with understanding its formation.

• Open an initial problem through search a particular issue ID or even form any issue ID
• On the right-hand side of the issue description screen, there will be three dots. Select it and options will be given
• Select the Create subtask from the menu
• There will be a window denoted, ‘Create subtask window’
• Enter the mandatory details and click on ‘Create’
• The created subtasks would be added to the parent issue under the subtask section
• There will be options as well to convert an issue into a subtask and a subtask into an issue.

29. Give an explanation for Kanban board.

The Kanban board is initiated for the projects where the team’s focus is on the visualization of the workflow and management of the work in progress of the project. The main attribute of the Kanban board would be that it is in work mode because the projects do not have their work as planned. The following gives a step instruction on the manner the Kanban board is created within JIRA.

• Log in to JIRA with the right credentials and navigate to the dashboard.
• Click on the project drop down and select ‘Create Project’.
• Select the moniker, ‘Kanban Software development’ and then click on the Next button.
• Enter the required information and select the Create button.
In the case of Kanban, the incoming task tends to give a higher priority and so it is viewed as the best method for bug fixing and maintenance release.

30. What is a scrum board?

The scrum board refers to a board, which was created with the utilization of the scrum preset. In the event a team is planning to work in sprints then the scrum board would be the one that is best for them.

31. What is the validator within JIRA?

The task of the validators in JIRA is to check that any input made to the transition happens to be valid before the transition is done. The issue does not progress to the destination point of the transition if the validator fails.

32. What is an issue collector?

The issue collector in JIRA allows the user to embed a JIRA feedback form within your website. This assists the visitors to the site to log issues into JIRA through the website. The visitors to the website have no need for a user account in JIRA in order to access the feedback form.

33. What is an Audit log?

The audit log in JIRA allows the administrators to consider the changes, which have been made to the website. The audit log also assists the end user in troubleshooting.

34. Name some of the reports, which are created by the Kanban projects in JIRA.

• Control chart
• Cumulative flow diagram

35. Give an illustration of reports generated by the scrum projects in JIRA

• Control chart
• Burn down chart
• Cumulative flow diagram
• Epic report
• Sprint report
• Version report
• Version chart

36. Give some reports which were generated in JIRA for particular issue tracking and analysis

• Created vs. the 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

37. What are the limitations that come with editing an active workflow?

The limitations apply during editing the draft for an active workflow.

• It is not possible for one to edit the name of the workflow • The statuses of the workflow cannot be deleted • The step ID cannot be changed • If the status does not have any outgoing transitions then it cannot have any transactions outgoing added, whether they are globally or regionally based.

38. What is an event in JIRA?

The event is classified according to a two-system event and custom event, which are for JIRA, and User-defined events respectively. The event describes the status, so the default setting and the notification scheme and workflow transitions post the function associations for the particular event.

39. In the JIRA workflow, is it possible for one to transition an issue to the previous status?

It is not usually possible to transition the problem back to the way it was. However, you can use an ‘on-hold’ element in order to transition the issue back to the previous status. The following illustrates some of the steps to take in this setting.

• When it comes to the workflow, create a global transition to the status of ‘On Hold’.
• Create another transition to every other status, which you would like to go to.
• Because the names are not the same, add a blank space at the end.
• You do not want the status to go from the ‘On Hold’ and ‘Done’ to the ‘On Hold’. That means you can proceed to hide the other status of ‘On Hold’, by adding the value field conditions for the transition.

40. Give a few mentions for the things, which can be configured, for the JIRA project and issue type.

It is possible to customize a number of things for each pair of an issue type and JIRA project.

• The workflow of the issue such as the statuses.
• The order of the custom illustrated on an issue screen
• The custom fields and the system that the issue may utilize.
• The accessibility of the project.

• The permissions for what the user can do with the issue. • The versions and different components that are there for an issue.

41. Give a similarity and a difference between the JIRA scrum and JIRA Kanban.

• Similarity: the JIRA scrum and the Kanban are said to be strong powerful process tools for optimizing work and the processes as both focus on the continuous optimization and visualization of the workflow. In these particular cases the complex and large are broken down and so each of the individual tasks are considered and completed in an efficient manner.
• Difference: the scrum board represents the work mode at the point where the progress of the sprints and tracking of the work is done. At this time the team considers the list of issues, which has become backlog and so these problems are moved toward the sprints according to the plan of the team. When it comes to the Kanban board though, the progress actions are maintained and the processes of their flow are tracked accordingly. In this setting, the team comes to a decision of the increase and decreasing of the issues, which are to be displayed in each status of the workflow.

42. What does programming associate in nursing mean?

Programming the issue implies that programming the issue for a particular due date. For this perform to figure, there needs to be a ‘Schedule issue permission’ by JIRA administrator. During this case, a field with ‘Due Date’ would be populated.

43. For explicit issues, what would be the square measure enclosed beneath the modification history?

Modification history section shows the activities that are related to fixing the records with information on the one who created the modification because this is the time the changes are created. The history also shows the data concerning the recent and new field values within the case of the modification in any field. The modification history is inclusive of the subsequent records of the changes. This would include the:

• Creation and deletion of a comment.
• Creation and deletion of difficulty links.
• Deletion of the work-log
• Issuing of field changes
• File attachment alterations

44. What are the most useful add-ons in JIRA? Some of the best add-ons include the following:

• Jenkins- CI
• Slack
• HipChat
• GitHub
• User snap
• Tempo Timesheets
• Pager Duty

45. What is noted under the JIRA schema?

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

46. Explain how it is possible to disable mail notification for bulk operations?

To disable mail notification for particular bulk operations, you have to remove the selection for the ‘send notification’ check within the bulk operation wizard.

47. What is a JIRA project key?

The project key is a three to four character length item that seems to appear for each big created within a specific JIRA project. Every project has to be licked to a project key during the initial stages of the creation of the project. This assignment is provided by the JIRA administrator. The admin then has the opportunity to change the key at the time of the project creation process and the key then would be screen across every scene for the corresponding undertaking.

48. What is JIRA Core?

This great workflow management system provides for the formulation of specialized processes. The utility allows for both the increase and decrease of the complex nature of the workflows. That would allow the implication of more importance given to the process. The good thing with JIRA Core is only the constraints on the workflow would be the processes.

author: patrick algrim
About the author

Patrick Algrim is an experienced executive who has spent a number of years in Silicon Valley hiring and coaching some of the world’s most valuable technology teams. Patrick has been a source for Human Resources and career related insights for Forbes, Glassdoor, Entrepreneur, Recruiter.com, SparkHire, and many more.


Help us by spreading the word