Q1. What does Jira stand for?
It provides bug tracking, issue tracking, and project management functions. The product name is a truncation of Gojira, the Japanese name for Godzilla, itself a reference to Jira’s main competitor, Bugzilla. … According to one ranking method, as of June 2017, Jira is the most popular issue management tool.
Q2. Can Jira be used for test case management?
While JIRA wasn’t designed to serve as a Test Case Management, it can be configured to support test case management in a couple of different ways. The JIRA platform is, at its core, our workflow engine that allows you to track issues or tasks through a predefined, highly customizable workflow.
Q3. What is Zephyr and Jira?
Zephyr for JIRA ( Server and Center versions) is a native application that exists in JIRA and brings test management capabilities to any JIRA project
Q4. How particular project details are listed in JIRA.
Every project has some main attributes which have to be displayed in the project summary. This attributes include:
- Name of the project
- Versions (if present)
Q5. What is a workflow?
Workflow is defined as a movement of the bug/issue through various stages during its life-cycle
Q6. Is it possible to access JIRA cloud site via a mobile device?
Yes, it is possible to access JIRA cloud site via a mobile device. You have to just use the URL of the JIRA cloud site in your mobile web browser.
Q7. What do you mean by Scheduling an issue?
Scheduling the issue means scheduling the work of 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.
Q8. Explain labeling and linking issue in JIRA?
Labeling 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.
Q9. Mention the types of reports generated in JIRA?
JIRA offer reports that show statistics for projects, versions, people or other fields within issues. Various reports included with JIRA are:
- Average Age Report
- Pie Chart Report
- Resolution Time Report
- Recently Created Issues Report
- Resolved vs. Created Issues Report
- Single Level Group by Report
- Time Tracking Report
- User Workload Report
- Workload Pie Chart Report, etc.
Q10. What does the three color indicates tracking times or duration for an issue?
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
Q11. What are most useful JIRA add-ons.
Some of the most useful JIRA add-ons are listed below:
- Tempo Timesheets
Q12. List out the source control programs with which it integrates?
It integrates with source control programs such as CVS, Git, Subversion, Clearcase, Visual SourceSafe, Mercurial, and Perforce
Q13. What does an issue change history include?
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
Q14. How you can share an issue with other users?
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.
Q15. 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 consist of 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
- Issue history
- Status and Resolution
Q16. Mention one similarity and one difference between JIRA Scrum and JIRA Kanban.
Similarity: Both JIRA Scrum and Kanban is considered as the most powerful process tool for optimization of work and the processes as both processes focus is on continuous optimization and visualizing the workflow. In these cases, large and the complex tasks are broken down and each individual tasks 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 has become backlog and then these issues are moved to sprints as per team plan.
In the case of 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.
Q17. How is security setting helpful in JIRA?
Security setting for any issue is defined or say set either at the time of creation of the issue or while editing the issue. The basic reason for security setting is to restrict the 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.
Q18. How you can modify multiple bulk issues?
To modify multiple bulk issues, you can use Bulk Change option from the “Tools” menu of the navigator. All the issues on the current page can be selected for the bulk operation. The following list details the available bulk operations like
- Workflow Transition
Q19. How you can disable mail notification for Bulk Operations?
To disable mail notification for a particular Bulk Operations, you have to de-select the “Send Notification” checkbox in the bulk operation wizard.
Q20. What is the use of “Move Issue” wizard in JIRA?
The move issue wizard enables you to specify another project in your JIRA instance. Move wizard permit you to change certain attributes of an issue like
Issue Type: If your issue is a custom issue type and does not occur in your target project, you must choose a new issue type for your issue
Issue Status: If you have assigned your issue as a custom issue status and it does not exist in your project, you must select a new issue status for your issue
Custom Fields: If you have determined required custom fields for your issue, which do not occur in the target project, you must set values for them.