Ans: 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.
Ans: 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.
Ans: Zephyr for JIRA ( Server and Center versions) is a native application that exists in JIRA and brings test management capabilities to any JIRA project.
Ans: Every project has some main attributes which have to be displayed in the project summary. This attributes include:
Ans: Workflow is defined as a movement of the bug/issue through various stages during its life-cycle.
Ans: 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.
Ans: 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.
Ans: 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.
Ans: JIRA offer reports that show statistics for projects, versions, people or other fields within issues. Various reports included with JIRA are:
Ans: Three color will be displayed representing the amount of time spent behind the issue.
Ans: Some of the most useful JIRA add-ons are listed below:
Ans: It integrates with source control programs such as CVS, Git, Subversion, Clearcase, Visual SourceSafe, Mercurial, and Perforce.
Ans: Issue change history includes:
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.
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:
Ans: 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.
Ans: 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.
Ans: 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:
Ans: To disable mail notification for a particular Bulk Operations, you have to de-select the “Send Notification” checkbox in the bulk operation wizard.
Ans: 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.