Introduction To JIRA Interview Questions And Answers
Jira is a platform-independent tool that has the capability to get executed across any operating system platform. It also supports multiple languages like English, German, Japanese, etc. The major Databases used by this product for backend support are MySQL and Oracle and SQL server. It can also be integrated with other tools like GIT, Clear case, Team Foundation Software, Mercury, etc. It is a closed source product and also available with a limited-time trial version .it is a licensed software with free license support for academic projects.
Jira is a premiere tracking product developed by an Australian company named Atlassian. the key tasks accomplished with JIRA are bug tracking, issue tracking, project management, workflow, and process management. it is basically implied for tracking bugs and issues related to mobile applications and software development.
- JIRA supports a large number of customizable business templates to manage simple and complex business workflows.
- Independent tracking of tasks is possible.
- Notifications can be dropped to users in the form of emails, comments, @mention, etc.
- JIRA supports more than 10 languages that are widely used as English (US, UK, India), French, German, Portuguese, Spanish, Korean, Japanese and Russian.
- JIRA supports more a large set of reports to track the progress of a specific time frame, deadlines, etc. Easy to recognize and produce diverse reports which intern helps to determine the progress of the team. Configuration of these reports is comparatively easy and the matrices can be displayed to the users in a much better manner.
Now, if you are looking for a job which is related to Jira then you need to prepare for the 2022 Jira Interview Questions. It is true that every interview is different as per the different job profiles. Here, we have prepared the important Jira Interview Questions and Answers which will help you get success in your interview.
Below are the 10 important 2022 Jira interview questions and answers that are frequently asked in an interview. These questions are divided into two parts are as follows:
Part 1 – JIRA Interview Questions (Basic)
This first part covers basic Interview Questions and Answers.
1. Explain the JIRA workflow?
A workflow mentions the series of steps involved in the life cycle of a bug or issue. they are as follow,
- CREATE: Create the bug or issue
- WORK IN PROGRESS: Here the entity enters into the fixed stage where a series of actions are performed to get this resolved
- CLOSED: Mentions the close of the entity.
2. Mention the Three Colour indicators?
This is the common JIRA Interview Questions asked in an interview. The Colour indicators in JIRA are Blue, Green, and Orange. they signify the time employed in troubleshooting an issue.
Blue: It pictures the Original time estimate time for the issue. The field will be labeled as ‘Estimate’
Orange: The Remaining time for getting the issue resolved. The field will be labeled as ‘Remaining’
Green: Signifies the overall time spent on the problem of reaching a solution. This field will be labeled as ‘Logged’
3. Explain JIRA project Key?
A three to Four character length item that appears for each and every bug and issue created in a specific JIRA project. Every project will be associated with a project jey at the initial stage of creating the project. This Assignation will be performed by a JIRA administrator. The admin has the ability to change the key during the project creation process and this key is screened across all instances of the corresponding project.
4. A short note on JIRA reports?
JIRA withholds a classified list of reports to depict the project statistics to the user. The key process involved in JIRA report creation process,
- Move to the desired project dashboard where the report has to be created
- Select the reports tab to view all the possible reports allowed for in JIRA
- Click on Switch report to view the different report.
these reports are diversified based on their need and attributes as follow
- 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
- Sprint Report
- Control chart
- Burn down chart
- Cumulative Flow diagram
- Epic Report
- Release Burndown
- Velocity chart
- Version Report
- Control chart
- Cumulative Flow diagram.
5. Change history elements for an Issue?
The change history section holds all the information on the change performed, a person who is involved in the change and the timestamp at which the change was done. To view change history for an issue open the specific issue, Under activity section select the history tab. the default records of a change history component are as follow,
- Create and delete of the issue link
- Create and deletion of a comment written
- Deletion of work log
- File attachment and detachment changelog
- Issue field level changes
Part 2 – JIRA Interview Questions (Advanced)
Let us now have a look at the advanced Interview Questions.
6. What is Jira Core, Mention its uses and who are Jira core project administrators?
It is an efficient workflow management system that allows formulating unique processes. this utility allows to both increase and decreases the complexity of the workflows. this allows implying more importance on the process involved. The beauty of JIRA Core is that the only constraints on your workflow are your processes
Uses of Jira Core :
- Run a t-shirt business
- setting up workflows that can manage your internal processes such as your design process
- your sales process, your manufacturing process, and even controlling your stock.
Jira Core Users :
Users are accountable for functioning with particular JIRA Core projects. They can provide access to the project’s issues based on their permissions, workflow transition, and closing on its completion.
Jira Core Project Administrators:
All the project configurations are managed by JIRA project administrators, they have the permissions for performing almost all configurations related requests. the major ones are modifying the look and feel of the project and configuration changes.
7. Explain Issue creation steps?
Step by step process on an issue or a defect creation in JIRA, these issues and defects are further been fixed by developers. Every issue will be tagged with an issue ID for reference.
- Log into JIRA
- Select create option, this will navigate to issue creation page
- Enter the following details on the issue creation page:
Project Field: Describes the project for which this issue is being raised.
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 much critical.
Attachment: Any files or contents related to the issue can be uploaded in this section.
Environment: Specifies the platform or the operating system in which the issue was encountered.
Issue Type: Mentions on the type of the issue determined
Reporter: Under whom the Issue is being raised
Description: A detailed summary of the issue, it includes statements like an actual result, expected result etc.
Fix version: Filled by the developer who is involved in solving the issue, who decide the version, the time of completing the issue and the status of the issue.
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.
- Once the above fields are filled the clicking the create button will generate the issue active for the developers to work on it and resolve.
Let us move to the next JIRA Interview Questions
8. Can an Issue be assigned to two different people, Explain Cloning issue, then what are linked issues?
JIRA does not support assignation of the same issue under two different people at the same instance of time. this maintains the stability that one multiple developer can never be tagged to the same issue ever. But at several instances based on the intensity and volume of work the issue or bug may generate there could be a possibility of tagging more than one resources to the same issue. so we can get this accomplished in JIRA by defining a subtask tagged to a different owner and then getting a relationship accomplished between the issue involved and this subtask. Also if a task remains uncompleted due to dependency on an intermediate one then this may trigger an aging issue and to avoid such scenario, JIRA does not allow one item to be assigned to more than one people at a time. In agile worlds, it is always preferable to avoid these kinds of dependencies because it affects the definition of done for one logical unit.
Issue Cloning: Issue cloning is the process of copying an existing issue, this is an alternative method which allows several users to work on a single issue, The process of cloning creates a duplicate with the exact information of the existing one. , the operation done either on the original issue or clone issue has no effect on each other. the exception items in the cloning process are
- Time tracking
- Issue History
- Status and Resolution
the process of issue cloning involves the below steps,
1) Open the issue by using its issue id.
2) If it is not under an existing issue create a new issue
3) On the right-hand side of the issue description screen, you will see “…”.
4)Select it displays the list of options.
5) Click on Clone from the displayed drop down option.
6) The clone issue window will be displayed.
5) We may edit the summary of the issue and click on ‘Create’ button.
7) Now a new issue will be created with the statement ‘Clone added in the summary of it.
Linked Issues: Linked issues is a different scenario two issues in JIRA are linked and hold some sought of relationship within them, unlike relationships are drawn within their sub-entities. Every linked issue may have a definition like “Blocked by or duplicate”. If you are writing a database procedure that needs access to a few tables and table access is a separate task, then you can link it. You can say that it is blocked by this issue. When a project is big and more and a number of owners are more, we may need multiple items created and can link them and define as a duplicate. When we are in the process of tracking bugs, it is possible for a scenario where only when a dependent bug is fixed then the main bug could be successfully resolved, these kinds of situations can be marked and reported as “blocks” in JIRA.
9)How to create subtasks in JIRA and explain issue cloning?
This is the advanced JIRA Interview Questions asked in an interview. Sub-tasking is the process of splitting an issue into small chunks of tasks and each of these can be tracked and worked impudently. The parent issue holds detailed information on all the subtasks created. all these task creation terms are confined to within a single project. Only if all the root tasks are completed then the primary parent task can be closed which establishes dependency in the process. the major steps involved in a sub-tasking process are as follow,
1) Open a parent issue by searching with an issue id or create any new issue id.
2)On the right side of the issue description screen, a small “…” clickable icon will be displayed. selecting this will display all the elements of it.
3) Click on Create Sub-task from the displayed drop-down option.
4)Subtask creation window is displayed
5) enter all the mandatory details like project field, summary, environment, etc in the window and select the create button.
6) This generates the subtask successfully under the respective parent.
7) There are also options available to convert an issue into a subtask as well as a subtask into an issue.
10. Adding Gadgets to JIRA dashboard?
Several gadgets can be added to JIRA personal dashboards. The JIRA admin is responsible for adding a gadget to a default dashboard of a JIRA application. no other users have permission to add these gadgets to the default dashboard. Several applications allow sharing of dashboards among a specific set of people, in such cases if one user makes a change to the dashboard the other people who share the dashboard could also see the changes.
A process of Adding a gadget to a dashboard,
1) Selecting the dashboard link will navigate the user to the dashboard
2) Select Add gadget button in the dashboard
3) Using the gadget wizard to pick the items preferred for adding
4) We can see a list of these gadgets in Gadgets for JIRA applications.
This has been a guide to the list of JIRA Interview Questions and Answers so that the candidate can crackdown these JIRA Interview Questions easily. Here in this post, we have studied top JIRA Interview Questions which are often asked in interviews. You may also look at the following articles to learn more –