Why is JIRA used?
Atlassian JIRA is essentially a difficulty and project following tool that permits North American nation to trace any project connected work by following a correct work flow. noncommissioned below are few reasons that verify the usage of JIRA:
Able to track project progress from time to time.
JIRA use-cases embody project management, feature implementation, bug following, etc.
Work-flow will be simply custom-made as per our demand.
Along with issue following, history of the work done on problems, when, what and by whom also can be half-tracked.
JIRA is platform freelance and may run anyplace.
Explain JIRA progress.
progress defines the series of steps or stages associate degree issue/ bug goes through throughout its lifecycle from creation to the closing of the problem. The progress here includes the creation of a difficulty, series of actions performed to repair the problem and also the last step includes the closing or say completion of the problem once verification
Enlist report sorts generated by JIRA.
There are multiple reports out there in JIRA that are wont to show the project statistics throughout the project life cycle. There are general reports out there for analyzing problems furthermore as totally different reports for commencement comes and Kanban comes.
Following are the overall reports generated as and once needed for analyzing issues:
Average Age Report
Created vs Resolved Issue Report
Pie Chart Report
Recently created Issue Report
Resolution Time Report
Time trailing Report
User Work Load Report
Version Work Load Report
Workload chart Report
Following are the samples of reports generated for commencement projects:
Sprint Report
Control chart
Burndown chart
Cumulative flow sheet
Epic Report
Release Burndown
Velocity chart
Version Report
Following are the samples of reports generated for Kanban projects:
Control chart
Cumulative flow sheet.
For generating reports for your project, follow the below steps;
Navigated to desired project dashboard.
Click on Reports tab from left-hand facet to look at totally different reports.
Click on Switch report back to read the various report.
Make a case for step by step however a difficulty is formed in JIRA.
Whenever a difficulty or defect is encountered whereas testing, it has to be according in order that the developers will work thereon and take the mandatory action to repair it. we’ll see step by step however a difficulty is formed in Atlassian JIRA.
1) Log in to your JIRA account by victimization valid credentials and obtain directed to the dashboard.
2) Click on ‘Create’ button displayed and you may be navigated to a window for making a difficulty.
3) Enter all the mandatory details form a difficulty. As you’ll see within the below image:
In Project field, project that we tend to are making a difficulty is chosen. during this example: STH_Learning(STHL) is chosen from the dropdown containing all the out there comes.
In Issue kind field, the character of the difficulty is chosen from the dropdown that contains choice like Bug, Task, Improvement, Story, New Feature, etc. during this example, ‘Bug’ is that the nature of the difficulty.
Justify the 3 color indicators and their significance.
For any explicit issue in JIRA, three colors like Blue, inexperienced and Orange is employed to denote the number of your time spent on any explicit issue. This info is displayed underneath ‘Time Tracking’ section. every color has its own significance like;
Blue: This color is to denote the ‘Original Estimate’ i.e. the time estimate to be invested with in resolution the problem. This field has been labelled as ‘Estimated’.
Orange: This color determines the time left for resolution the problem. This field has been labelled as ‘Remaining’.
Green: This color defines the particular time that has been used or say spent in resolution the problem to date. This field has been labelled as ‘logged’.
For any explicit issue, what all square measure enclosed beneath modification history?
Modification history section displays the activities of fixing any records with info concerning the one that has created the modification still because the time at that the changes are created. The modification history additionally displays the data regarding the recent and new field values within the case of the modification in any field. Basically, modification history includes the subsequent records of the changes:
Creation and deletion of a comment.
Creation and deletion of a difficulty link.
Deletion of a worklog.
File attachment changes
Issue field changes
The modification history for any issue are often viewed in JIRA by following steps:
Open any explicit issue.
Click on ‘History’ tab gift within the ‘Activity’ section.
Mention the simplest way with that a difficulty is often shared with different users in JIRA.
A difficulty is often shared with different users in JIRA by exploitation the share choice out there on the difficulty description page.
When share choice for any specific issue is clicked, it contains the link to the difficulty to be shared beside ‘Username or Email’ and ‘Note’ field that needs to be crammed.
What’s the importance of labeling issue?
Labeling a problem is largely done to categories a problem at intervals a selected section that successively will be simply searched with the assistance of labels. Label for a selected issue will be at the start set at the time of making the problem, whereas it will edit conjointly at intervals the problem. Label field is displayed beneath the ‘Details’ section as shown below within the figure:
What does one mean by programming Associate in nursing issue?
Answer: programming the problem suggests that programming the work of issue for a specific ‘due date’. For this perform to figure, one should have ‘Schedule issue permission’ by JIRA Administrator. during this case, a field with ‘Due Date’ is being inhabited.
Justify however specific project details square measure listed in JIRA.
Each project has some main attributes that need to be displayed within the project outline. This attribute includes:
Name of the project
Key
Components
Versions (if present)
What area unit problems sorts that area unit created and caterpillar-tracked via JIRA?
JIRA has some outlined set of default issue sorts that area unit displayed below ‘Issue Type’ section. alternative issue sorts are often additional, emended and deleted as per demand of the project. a number of the common issue sorts area unit Bug, Task, Sub-task, Epic, Story, etc.
Explain however you’ll be able to disable mail notification for Bulk Operations?
To disable mail notification for a specific Bulk Operations, you’ve got to de-select the “Send Notification” checkbox within the bulk operation wizard.
Explain however you’ll be able to modify multiple bulk issues?
To modify multiple bulk problems, you’ll be able to use Bulk amendment choice from the “Tools” menu of the navigator. All the problems on this page may be elect for the majority operation. The subsequent list details the on the market bulk operations like
Work
low Transition
Delete
Move
Edit
Explain however you’ll be able to share a problem with different users?
You can email a problem by victimization the share choice in JIRA. you’ll be able to conjointly email different JIRA users a link to the problem by sharing the problem with them or by mentioning them in AN issue’s Description or Comment field.
When you log defect victimization TestDirector or JIRA what fields does one see?
When we log a defect, we have a tendency to see Defect ID (it shows later in Test Director), outline (where we have a tendency to write short description of the defect), Description (long description of the defect), Detected by (Person World Health Organization found the defect, (it’s you), Severity (meaning-is the defect critical? High? Medium? Or Low?), Date, Detected in Version, Priority, Project, Status, appointed to and then on. Click the link below to ascertain the fields once you report defects in JIRA or Test Director:
Defect Fields in JIRA
List out the supply management programs with that it integrates?
It integrates with supply management programs like CVS, Git, Subversion, ClearCase, Visual SourceSafe, Mercurial, and Perforce.
What will a difficulty amendment history include?
Issue amendment history includes
Deletion of a comment
Deletion of a worklog
Creation or deletion of a difficulty link
Attachment of a file
Changes to a difficulty field
What may be referred as a difficulty in JIRA?
In JIRA, a difficulty may be something sort of a
Software bug
The project tasks
A help-desk price ticket
The leave request type
Is it potential to access JIRA cloud web site via a mobile device?
Yes, it’s potential to access JIRA cloud web site via a mobile device. you have got to merely use the computer address of the JIRA cloud web site in your mobile application.
Are you able to disable JIRA mobile for the site?
You can disable JIRA mobile for the positioning, in order that users are often unable to work the desktop read of JIRA on their mobile device. JIRA mobile comes as a system add-on and might be disabled any time.
Justify labeling and linking issue in JIRA?
Labelling Issue: It allows you to reason a problem in an exceedingly additional informal manner than assignment it to a element or version. you’ll then search problems per label.
Linking Issue: This feature allows you to link associate association between 2 problems on either on similar or completely different JIRA servers.