It is an issue tracking tool developed by Atlassian. The first version of this tool is released in 2002. The software is written in java language. The name “Jira” is taken from the Japanese word ‘Gojira’ which means ‘Godzilla’. This tool is widely used for issue tracking and project management in approximate 120+ countries. it contains many functions which make issue handling very easy. It is an Agile project management tool that supports Agile methodology.
This tool offers three packages:
Jira Core: It is the basic tool that is used for project management and task management. In this tool, every person in the organization can plan, track, and report the work.
Jira Software: It provides agile functionality. It also includes scrum and kanban boards. The package includes issue tracking, progress reports, email notifications, customizable workflows.
Jira Service Desk: Jira service desk is simply modern, collaborative, affordable, and powerful ITSM( IT Service Management) software. It is a flexible software that is built for rapid service delivery.
How to download Jira
It is a defect tracking and project management tool. You need to buy the license to use this tool. This tool also offers a trial version that can be used by you.
You need to login to this tool, you can login to this tool by your google account. Once the account is created, you need to provide a site name which will be used for your tool.
What we can do in this tool
- We can create backlogs by using this tool.
- We can create sprints in this tool.
- Different tasks can be created in this tool.
- You can update the story status in the scrum board.
- Write and execute test cases, update the status of the test cases.
How to create a project
- Click on the project and select create a project. A new window will open in which you need to enter the project name and key.
- Click on create project and after this a new dashboard will appear which will look like this.
Now we will learn about some important terms which are epic,story,task.
In this section, business needs are defined. It is a bigger set of requirements. For example. As a user, I need to use the online shopping application is the epic.
In this section, customer needs are defined. When the epic requirements are Broken into smaller requirements, then those smaller requirements are known as stories. An epic can be divided into many stories. For example, The above example can be broken into smaller requirements:
- Story 1: As a user, I can log in to an online shopping application.
- Story 2: As a user, I can check my items in the cart.
Stories can be further divided into tasks that defines the solutions for particular stories. The story can be divided into multiple tasks. For example:
- A developer can review the story.
- Estimate the time required for the story.
- The developer needs to start designing.
- The developer will start the coding.
- A developer will perform integration testing etc,
Quality Analyst Tasks:
- The QA will review the story.
- A QA will make test cases.
- The QA will be responsible for test scenarios.
- The QA will prepare test data.
- Then the QA will review those test cases.
- The test environment will be prepared.
- The test cases will be executed by the QA.
- Bugs will be reported by the QA etc.
Once the developer and QA tasks will be completed, the story will be completed and the demo version will be released.
- Scrum Master will be managing the whole Agile Development Team.
- He will note down the challenges faced and will find the solution for them.
- They will be responsible for driving the Agile process.
- He will be responsible for getting the requirements from the customer.
- He will define the features of the product.
- The releasing date and content will be decided by the product owner.
- He will accept or reject the work status.
- Scrum team includes Developers and Quality Analysts.
- They are the actual executors.
Complete Agile Scrum Process
Product Backlog: It is prepared by the product owner which will contain the requirements received from the customer.
Now suppose a customer wants to include 10 features/stories in the project then we will not deliver all the stories to the customer in a single iteration. We will divide these into multiple sprints. These 10 stories can be divided into 3 to 4 sprints and each sprint usually lasts for 2-3 weeks. After completion of each sprint, a demo version of the product is released.
Let us understand the whole process in simple steps:
- The product owner will receive the requirements from the customer.
- The product owner will prepare the product backlog and set up the stories.
- A sprint planning meeting will be organized in which the development team and QA team will select the stories which will be completed first. The product owner will divide these stories into different sprints according to the story point.
- A story point is the estimated time given by the tester and developer for the specific story.
- The product owner will interact with the developer and tester and they will decide which stories will be completed in the first sprint.
- The product owner may ask the scrum team to complete 5 stories in the first iteration. If the scrum team finds that the stories are difficult then they can say that due to the high difficulty level, we can only complete 2-3 stories in this sprint.
- The sprint backlog contains the committed stories. These stories are committed by developer and tester. If in a sprint, the tester, and developer fails to complete the number of committed stories then the uncompleted story goes back to the product backlog and then it needed to be completed in the next sprint. The tester and developer need to justify the reason for not completing the story. For every story, the developer and tester will be responsible for their individual tasks.
- Daily scrum meetings will be organized.
- The scrum master will monitor the whole process. He will review the work and will be responsible for the whole process. In case of any challenges, he is the one who will contact the management.
- After the completion of the 1st sprint, the demo version will be released and delivered to the product owner/quality analyst/developer.
Once the sprint is completed, a sprint retrospective will take place. In this we will discuss:
- What went wrong in this sprint.
- What went well in this sprint.
- Where we can improve.
Issue types in Jira
We have four types of issues:-
You can add Test issue type after installing the Zephyr Plugin.
Create Epic and Stories
Once you have created the project, you can now create issues. Click on the create issue and select any one of them from the drop-down menu.
You can create Epic, Stories, Tasks, and bugs with this option. Here we will be creating one epic and five different stories. Once you create the epic and stories, then you have to click on the backlog which will appear like this:
In the given screenshot, we have created epic as onlineshopping_0001 and for this epic 5 different stories have been created. The stories are login page, cart page, listing items, wishlist, and payments. The numbers like ‘5’, ‘3’ are the story points.
Create and start sprint
After creating stories and epic, we need to create sprints. After creating sprints, we need to add stories to these sprints. For example, if we want to complete 2 stories in the first sprint then we will add two stories to that sprint.
In the given screenshot, we have added two stories to the first sprint which has story point 5, and three stories to the 2nd sprint which has story point 3.
Once you have created the sprint, we need to start these sprints one by one. When you click on start sprint, a new window will open . in this window, you need to enter the name of sprint and need to set the duration of the sprint. In the last option, you need to enter the goal of the sprint.
Add tasks to the stories
Now developers and QA will be responsible for completing their individual assigned tasks. Here we have attached the screenshot in which different tasks are created.
In this given snapshot, we have created QA tasks and developer Tasks then the individual person will be responsible for completing the assigned task.
Sprint status in Jira
There are three types of sprint status in Jira:-
- To Do
- In Progress
Creating Bugs in Jira
When creating bugs in Jira, you need to set the priority of the bugs. You can set the priority from the given options from the drop-down menu:-
You need to select the issue type as bugs and then you need to enter the summary of the bug. The priority needs to be set and then you can assign the bug to the user.
These are some steps for creating epic, stories bugs, sprints. We have attached screenshots for each step. You can easily learn the Jira by following this tutorial.
Create test cases in Jira with Zephyr Plugin
You need to install the Zephyr plugin first. You need to search the plugin in the apps. Search the Zephyr plugin here. The following result options will appear.
You need to install the Zephyr for Jira – Test management from the options. Once you click on install, the plugin will be installed after some time. Once you install the plugin, you will be notified after installing the plugin. The dashboard will appear like this:
The dashboard will appear like this. The zephyr option will be added in the menu.
How to add issue type”Test” in Zephyr
After installing the zephyr plugin, you need to add the issue type”Test“. This can be done by following the simple steps which are as follows:
- You need to go to Project Settings.
- You need to select the add issue type.
- Select test.
Now the test issue type will be added.
Create Test Case
Now you need to create the test case. The test case can be created by clicking on the create test button.
You need to select the issue type as “test” and then you need to enter the summary of the issue. Click on create the test case and the following window will appear:
Once the test case is created , you have to click on the test case. Once you click on the test case, the following window will appear:
When you click on this option, the above given window will appear. In this window , you need to add test step, test data and test result. For example, you can enter following information:
- Click on the login button
- Enter the user name.
- Enter the password.
The user registered successfully.
Once you enter this information, click on save all the information. When you click on save, the test case will be created.
Create a test cycle
After creating the test case, you need to create the test cycle for executing the test cases. Click on the test cycle and then click on create a new test cycle.
You need to select the version as unscheduled and then you need to enter the name of the test case. In this case, we have entered the test cycle name as a Functional test case.
Once you have created the test cycle, you need to enter test cases to this test cycle.
In this snapshot, we have clicked on the backlog and then selected the test case. After selecting the test case, click on the button on the extreme right corner and the following options will appear. As you can see in this menu, the Add to the test cycle(s) option will appear.
When you click on Add to Test Cycle(s), the above window will appear. You can select your newly created test cycle from the cycle summary. Then you need to assign the test cycle to the user. Finally, click on the add. The test cases will be added to the test cycle.
Execute Test Case
Once you have added the test cases to the test cycles, you need to run/execute the test cases. Once you click on the cycle summary, the following window will appear:
In this window, you can see the execution status. The execution status consists of following options:
When you click on the pass, the green color will appear on the pass button and the test will be executed. The tests can be executed manually or through automated tools.
By following the above steps, the test cycles are created and test cases are executed.
If you want to know / view the test report, then you can click on the Report. The below window will appear. Here you can check all the information related to the test cases.
In the reporting section, you can view all the information like test case executed, total no. of tests, total number of unexpected tests etc.
By clicking on the report, you can check:-
- Test Summary
- Test Metrics
- Traceability Matrix
This is the complete tutorial of Jira. I hope this tutorial will help you in clearing all of your doubts regarding this tool. If you have any questions related to this topic, you can mail us on [email protected] or do let us know in the comments. In the next topic, we will discuss the top questions on the basis of Jira.
Click here to read the top 10 questions which can be asked during the TCS interview.