Jira Tool | Agile Project Management

Summary

This video provides an in-depth guide on using the Jira tool for agile project management, focusing on its role in organizing tasks within a software development cycle. It describes how Jira separates tools into management and automation categories, and explains its functionality in tracking agile processes such as sprints and stories. The video outlines steps for setting up Jira, creating projects and backlogs, and introduces creating epics and stories within them. It further elaborates on assigning tasks to developers and testers. Additionally, the guide covers installing plugins for expanded test management capabilities, like Jfr, which facilitates importing test cases and executing test cycles. The session underscores Jira’s benefits as a comprehensive tool in unifying different management and tracking activities within one platform, emphasizing efficient project monitoring and execution.

Highlights

• Jira supports both management and automation tools essential for efficient software testing. 🤖
• Using Jira makes bug and defect tracking intuitive and streamlined. 🐞
• Easily creates and manages agile workflows including epics and stories. 📚
• Facilitates a comprehensive board view of tasks across different sprint stages. 📋
• Automatically generates crucial charts and graphs like burn-down and velocity charts. 📈

Key Takeaways

• Jira is a powerhouse for managing agile processes, from backlog to sprint execution. 📊
• Proper configuration of Jira can streamline project management and improve efficiency. 🚀
• Jira’s test management can be expanded with plugins like Jfr, making it versatile. 🔌
• The tool incorporates both agile and testing workflows seamlessly, avoiding the need for multiple software. 🌟
• Detailed exploration of creating, tracking, and executing tasks preserves project integrity. 🔍

Overview

In today’s session, the focus is on getting acquainted with Jira as a vital tool in agile project management. The video kicks off by describing the various tools available in the software testing industry, segregating them into management and automation tools. This foundation paves the way for understanding how Jira fits into managing agile processes, emphasizing the critical role it plays beyond just bug tracking.

Deep diving into Jira's setup, the session guides you through creating projects, backlogs, and defining epics and stories. It highlights how these elements can be effectively managed within the Jira platform, ensuring tasks are tracked and executed efficiently. The video is rich with step-by-step processes, ensuring that both beginners and seasoned users can align with agile methodologies deployed via Jira.

Moreover, the video underscores the addition of plugins like Jfr, illustrating how they can enhance Jira’s test management capabilities. This demonstrates how developers and testers can integrate their workflows into Jira, rendering a holistic view of project management. Jira stands out as an indispensable tool, bringing together various facets of agile project management seamlessly under one roof.

Chapters

• 00:00 - 03:00: Introduction to Jira and Overview of Tools in Software Testing This chapter introduces the Jira tool and provides an overview of various tools used in software testing. The session begins by outlining the objectives of Jira and its functionalities. It sets the stage for understanding different categories of tools available in the industry, such as bug tracking tools, test management tools, functional automation tools, and performance testing tools.
• 03:00 - 05:00: Test Management and Bug Tracking in Jira The chapter discusses the variety of tools available in the market for security testing, emphasizing the division into management and automation tools. It highlights the importance of understanding the processes followed, documents prepared, and activities involved in using these management tools.
• 05:00 - 07:00: Agile Tools and Jira's Role This chapter discusses the role of tools in Agile, particularly focusing on test management tools. It emphasizes the advantage of using tools over traditional templates like Word or Excel for tracking, organizing, and managing tasks throughout the testing life cycle. The chapter underlines the efficiency and effectiveness of integrating these tools, such as Jira, into the testing workflow to ensure smooth operation and management of tasks.
• 07:00 - 10:00: Jira in Agile Project Management This chapter discusses the role of Jira in Agile Project Management, emphasizing its significance in testing activities and the Software Testing Life Cycle (STLC). It highlights how requirements can be defined, test scenarios written, test cases executed, and bugs reported and finally closed within the tool, as opposed to traditional template-based methods. The chapter also touches upon different categories of tools, including test management tools and bug or defect tracking tools, showcasing how they support and streamline these processes.
• 10:00 - 15:00: Installing and Configuring Jira Chapter Title: Installing and Configuring Jira The chapter discusses the usage of defect or bug tracking tools, particularly emphasizing the function of Jira in managing defects. It explains how bugs can be reported by providing a defect description, setting priorities, and attaching screenshots. The process allows for efficient communication between testers and developers, with developers addressing the reported defects accordingly. The chapter is an introduction to setting up and configuring Jira specifically for defect tracking purposes.
• 15:00 - 21:00: Creating Projects and Managing Users in Jira The chapter focuses on the importance of understanding differences between tools, particularly test management tools, which is crucial for beginners. It emphasizes that in interviews, one may be expected to know these differences. Test management tools allow users to track every activity related to the testing process, including writing test cases, executing them, and reporting bugs. This tracking is essential for effective project management in Jira.
• 21:00 - 26:00: Creating Backlogs, Epics, and Stories The chapter discusses the tools used for creating backlogs, epics, and stories in project management, specifically focusing on bug tracking and defect reporting. It explains that bug tracking tools are essential for identifying, reporting, and tracking software defects or bugs. The discussion highlights that these tools help in managing backlogs by ensuring that all detected issues are documented, tracked, and prioritized effectively.
• 26:00 - 31:00: Sprint Planning and Management in Jira The chapter 'Sprint Planning and Management in Jira' discusses the role of automation tools such as Selenium and QTP in the testing process. These tools help automate test cases to streamline testing activities. It further explores the use of process-related tools for managing and maintaining testing activities, specifically focusing on test management tools that also include features for bug reporting. This is considered an integral part of the Software Testing Life Cycle (STLC).
• 31:00 - 39:00: Task Assignment and Management in Jira In this chapter, the focus is on how task assignment and management are handled within Jira, a popular tool in the domain of agile project management. The chapter highlights the use of test management and bug tracking tools, indicating that Jira serves not only for these purposes but also excels as an agile tool. Specifically, agile tools, including Jira, are crafted to automate the agile process, helping teams efficiently track agile tasks as part of the broader agile process.
• 39:00 - 45:30: Bug Reporting and Test Management Introduction In this chapter, the process of bug reporting and test management is introduced, beginning with a discussion on Apex stories defined by the product owner. The sequence moves through several phases, starting from the creation of a product backlog to the sprint planning meeting. During this meeting, some stories from the backlog are selected to prepare the sprint backlog, with commitments from development and QA teams. The sprint, lasting between two to four weeks, takes these stories through various stages, beginning with story development.
• 45:30 - 49:00: Installing JIRA Plugins for Test Management The chapter discusses the process of integrating JIRA plugins to enhance test management. It describes various stages involved in deploying and testing within an agile framework. The transcript mentions the steps leading up to the closure of a story, including demonstrating the story to the product owner, and eventually releasing it to the customer. It highlights the use of agile tools to define, track, and manage these activities effectively.
• 49:00 - 57:00: Managing Tests, Cycles, and Execution in Jira The chapter discusses how to manage tests, cycles, and execution within Jira, focusing on maintaining scrum boards or storyboards directly in the tool. It highlights the ability to automatically generate various graphs such as burn down charts and velocity charts. These tools allow for the tracking and definition of activities in the agile process, emphasizing the capabilities of agile tools available in the market.
• 57:00 - 58:00: Final Thoughts on Jira's Capabilities The chapter discusses the various tools available in the market for agile processes, with a focus on Jira as one of the most popular and widely used tools. It also mentions other tools like Version One and Team City, highlighting that there are both free and open-source options available. These tools aid different activities within agile processes.

Jira Tool | Agile Project Management Transcription

• 00:00 - 00:30 all right so let us start today's session so  today's session is uh how to use jira tool   okay so before using the jira tool let us try to  understand what is jira so what it is contains   what is exact purpose of jira tool okay so we  have multiple types of tools are available in the   software testing industry guys okay so we have uh  bug tracking tools we have test management tools   right so we have uh automation tools functional  automation tools performance testing tools
• 00:30 - 01:00 security testing tools so there are n number  of tools are there in the market especially for   testing okay and these are different uh different  type of testings we have a different type of tools   and again we can divide these tools into two  different parts one is management tools and   the other one is automation tools so what is  a management tools means what is the process   we are following and what are the documents we  are preparing or what are the activities we are
• 01:00 - 01:30 doing throughout the testing cycle we can uh  track all these activities in a tool instead   of using the templates or instead of using word or  excel templates we can track all these activities   in a tool so they are basically comes under  test management tools so whatever activities   we are doing throughout the testing process  or throughout the testing life cycle we are   organizing the uh tasks or managing the tasks  or tracking the tasks in a tool those tools   are comes under test management tools so what  we can do in the test management tools we can
• 01:30 - 02:00 define the requirements we can write the test  scenarios test those cases and we can update the   test case execution status and we can report  the bugs okay and finally we can close the   requirements so all these things are testing  activities stlc so these activities we can do   in the tool itself instead of using  the templates so that is they are   some tools support these activities so those  tools are comes under test management tools   there are some other tools called bug  tracking tools or defect tracking tools
• 02:00 - 02:30 and those tools will be used only for defect  tracking so whenever you find a bug you can report   the bug through that particular tool instead of  using templates so you can just write the defect   description priority cvrt steps you can attach  the screenshot i can send it for developer and   developer will take care of the defect so they are  all comes under the defective tracking tools or   bug tracking tools that is another type of  tools we have okay and let me just write here
• 02:30 - 03:00 understand the difference which is very very  important as a beginner guys okay people may   expect something in interview so do you know  the differences between these tools or not   so the test management tools test management  tools okay so each and every activity we can   track in the test management tools like  from the beginning test cases writing test   cases execution bug reporting everything  we can track in the test management tools
• 03:00 - 03:30 and uh similarly we also have bug tracking tools  backtracking tools are defect tracking tools   and these tools only for backtracking or defect  reporting tools or we can say uh bug reporting and   tracking tools bug reporting and tracking tools  we can say defect reporting and tracking tools   also anything is fine so these are the two main  tools we have apart from this okay we also have
• 03:30 - 04:00 automation tools like selenium qtp these are all  test automation tools so whatever test cases we   have we can automate those test cases because they  are the completely different tools and these are   the process related like what are the activities  we do during the testing we will automate all   these process tasks like we can track how we can  maintain the activities in those particular tools   so test management tools and back reporting and  tracking tools again the test management tools   also having features of bug reporting so this is  also part of stlc so test management tools when
• 04:00 - 04:30 i use test management tools we can also use it for  bug tracking purpose okay but apart from these two   there are other other type of tools called agile  tools okay agile tool so what is agile tools or   agile tools means basically these tools especially  designed for automating the agile process okay   especially these tools are designed for tracking  the agile tasks like in agile process uh in the
• 04:30 - 05:00 previous session we have discussed about the  lot of things like from the apex stories we   will define by the product owner and then uh after  that we will have product backlog then we have a   sprint planning meeting then we will select the  sum of the stories from backlog and we prepare   the sprint backlog uh which contains some of  the stories which are committed by the devon qa   then we will have a sprint and the sprint duration  will be two to four weeks of time and once you   start a story which will go to different  stages like starting the story development
• 05:00 - 05:30 testing deployment so multiple stages the story  will go on and finally we will close all the   box related to the story and we close the story  and we will demo the story to the product owner   and finally release to the customer so in this  agile process whatever activities we are doing   so to define these activities and tracking these  activities we have a different tools called agile   tools and all the scrum related activities we will  perform in the agile tool itself and we can also
• 05:30 - 06:00 maintain the scrum board or storyboard in the tool  itself and we can generate the graphs like burnt   burn down chart and velocity chart so all these  things we can automatically generate in the tools   and uh everything we can do whatever activity  even the small activity whatever you do in   the agile process we can track or we can  define those activities in the hl tool   okay so that is all about agile two so  what are the tools available in the market
• 06:00 - 06:30 as part of hl we have most popular tool is  jira okay and apart from this jira we also have   something called uh version one so this is also  one of the tool which is available in the market   okay and uh team city okay and uh there are  multiple tools are available in the market   some of them are free some of them are open  source okay okay these are all comes under   the agile tools means each and every activity  in the agile process agile process contains
• 06:30 - 07:00 again development activities testing activities  everything will be part of agile so these tools   will assist you to define each and everything  which we follow in the agile process okay   so these are the tools which are examples of agile  tools so now we are going to discuss about jira   tool so jira is a purely agile management tool  we can say agile management tool each and every   activity we can define we can track in jira tool  itself and this tool can be used by developers
• 07:00 - 07:30 tester product owner so or is working on the team  in the gel team they have access on jira tool   okay so in the jira we will do lot of activities  so i will just show you what are the activities we   do first we i'll list out here and then we will do  step by step okay so what is jira so we understood   what is jira so jira is a agile project management  tool or we can say agile management tool jira is
• 07:30 - 08:00 a agile management tool means which includes the  development activities testing activities product   owner everybody will track everything in jira  itself we should not go out of jira tool even   in jira we can also do test management activities  but jira itself is not providing any test   management activities by default so by default  jira in jira we cannot define the test cases bugs   and everything but we have a special plugin called  j fire and if i install that particular plugin in
• 08:00 - 08:30 within the jira we can also do test management  activities right we can also define the test   cases we can write the test cases we can upgrade  the status of the test cases we can report the box   okay and we can generate the test sim test  reports everything we can do in the jira itself   by by using jeff fire plugin along with the jira  okay apart from the agile management activities
• 08:30 - 09:00 so we will see all of them practically so first  of all let us start so first we will see how to   install and configure jira tool okay and there  is some workflow is available so we need to   follow that workflow jira workflow so what is  the jira workflow so let me just write here   jira can be used in two different angles guys okay  the first thing is we will see how we can use jira   for tracking the agile related activities what is  mean what is meant by gel related activities first
• 09:00 - 09:30 we will have creation of project and then we will  have a backlog which contains different stories   epics and stories we will define and after that  we will create a sprint and we will add stories to   the sprint and then we will start our sprint which  will go two to three weeks of time or four weeks   of time and during the sprint there are multiple  tasks we are going to do for that particular   story so for that partly story and developer and  testers both will write their tasks for each story
• 09:30 - 10:00 and they will cover they will complete  those tasks during the period of time   or sprint time and finally we will close the  story so this is called as a workflow okay once   a story is defined by product owner the story  will go to different stages till it is closed   okay so that is basically called as a workflow  so that is agile process agile workflow in jira   and apart from this we also have a test management  activities right that is a different workflow
• 10:00 - 10:30 again so once you install jeff fire plugin within  the jira we have to follow a different workflow   to perform test management activities like first  we need to uh create our test cases or we can   import the test cases suppose in excel you have n  number of test cases so you need to upload all the   test case at once in the jira you can also do that  you can import all the test cases once instead   of writing each test case individually takes time  so you can import all the test cases in jira once   and then we can create a test cycle then we'll  add the test cases to that particular test cycle
• 10:30 - 11:00 then we can execute the test cases and if there  is any failure we can report the bugs and then   we will generate the reports so these are all test  management activities so these activities also we   can do in the agile or in the jira tool and it is  also having a different workflow okay so first we   will see agile part and then we will come to the  test management activities how to write test cases   and everything we will see later okay so that is  all about workflow jira workflow so first let us
• 11:00 - 11:30 start with uh agile related activities how we can  do agile related activities in the zera tool okay   the first and most important thing is i'm going  to show you so what are agile or scrum activities   okay so i'll just list out here step by step one  by one and then we will see how we can perform   them in jira tool so before doing that i'll show  you how to install and configure jira tool okay
• 11:30 - 12:00 so first we will see how to install and configure  xero tool so jira is basically uh available okay   let me discuss this later so how to install and  configure jira tool this is the first thing which   we need to do okay so jira is basically agile  management tool okay so which is available in   two different flavors so which is available in  the two different flavors and if i just go to
• 12:00 - 12:30 jira official website i'm just searching jira tool  okay and this is from atlassian company so this is   a company and this is a product-based company  they will develop different type of products   and jira software is a one of the product of  atlassian company okay so now just click on   this atlassian.com software jira and if i just  look at here these are the different products   they develop from the atlassian company and jira  software is one of the most popular software
• 12:30 - 13:00 for agile jira software okay now if i just uh  click on this jira software you will get some   information about the jira tool so this is a page  you will get and they said it is a free number one   software development tool used for agile teams  so it they said it is get it free but this is   free only for 30 days okay and this software we  no need to download okay we can also download
• 13:00 - 13:30 install but it is again a complex process we need  to set up a server and everything so instead what   you can do is we can create a jira instance on the  cloud so cloud means what they allocate some space   and they will configure jira for us and  they will provide the link to us so we   can use that link and we can work with the jira  tool for 30 days okay so the jira is available   on the cloud so they will we can create our cloud  instance for jira software and we can use it for
• 13:30 - 14:00 30 days okay if you want to plan any practice  anything so within 30 days we can finish it out   okay so this is for 30 days if available  and in within the 30 days within the 30 days   or 10 members you can use the software because  in the jira there are multiple people are   using right product owner testers developers  scrum master so multiple team members will be   using jira tool right so all the users should be  part of the jira tool so this particular cloud
• 14:00 - 14:30 instance will support maximum 10 users okay so  within 30 days we can add 10 users and you can   work with the zero tool so that is the limitation  which we have on cloud instance okay so they have   given some information about this jira tool  and workflow here you can just look at here   so open in progress under review final approval  done this is a small workflow of agile as per jira
• 14:30 - 15:00 tool and some other information also they have  provided in this particular website you can just   go through this later so how we can uh con how we  can install and configure jira tools so basically   they have provided jira in two flavors okay  one is uh in the cloud itself we can have   two types of instances one is a free version and  10 users are limited and the other one is if you   want to still continue after 10 days sorry after  30 days 10 users 30 days okay so after you want to
• 15:00 - 15:30 continue with uh 0 after 30 days or if you want  to increase number of users then you have to go   with provisional version so this is a licensed  version on the same cloud the same url you can   still use it but you need to pay for uh the jira  tool so we need to buy some license for that which   is professional version which is available for 30  days 10 users we can access freely on the cloud
• 15:30 - 16:00 okay so nowadays most of the companies are going  with the cloud instances guys okay they are not   setting up any environment in there locally  they are not ready to setting up any machines   to install a complex softwares so most of the  companies are moving to the cloud so nowadays   cloud technologies are becoming very very popular  so similarly most of the software's also companies   are offering on the cloud environment directly so  we can have an instance on the cloud and we can
• 16:00 - 16:30 use it for our company and as many days i want so  after that after i completed my work i can close   it okay so some companies uh initially they offer  a free of cost and after uh some duration we need   to pay for them to maintain our instances on their  cloud environment okay so now jira is available on   the cloud and basically they are offering two  flavors one is free version 30 user for 30 days   we can use and then if you want to still continue  we can go with provisional version which is
• 16:30 - 17:00 licensed version okay so now let us see how we  can get the cloud instance to work with the agile   okay so now i'll show you step by  step so please concentrate on this   so what we need to do is i'll just provide you one  small link which will go to jira download location   okay this is a link so if i just go to this link   or you can just go here also you can just go  to jira software and you can i have provided
• 17:00 - 17:30 direct link here or else you can just  go here get it free click on get it free okay now you can just look at this website  and this page you can get and if i just look   at support up to 10 users or three agents and  includes the 2 gb of storage offers community   support it always free no credit no card  needed but it is only for 30 days okay
• 17:30 - 18:00 right so they have given two things here  confluence and jira service management   so we don't need to come go for confidence  it is only for document collaboration tool   and we need to go for jira service management  okay or else you can just click on the next   no need to select anything okay  just click on the next and here which will show you a few things so here  it will ask you the login guys okay so
• 18:00 - 18:30 first of all before creating the cloud instance of  jira you have to use your gmail account okay with   that gmail id which will create a new instance  so here you can just provide your gmail account   so what i will do is i'll just provide my  email account so sign in with a different   assistant account i'm just at large  an account i'm just clicking on this   and you can provide your gmail id just a moment  so first time uh it will ask you to provide your
• 18:30 - 19:00 gmail address so i'm just choosing  the continue with the google and   i want to use my gmail account so i have multiple  accounts i'm just using one account here my gmail   account existing account i need to just provide  the password here and then click on the next so   your gmail account will be used as your jira  account okay then now it will go to another screen
• 19:00 - 19:30 so once you provided your gmail account okay  now you can just look at here this is a gmail   id currently you are using okay to create your  jira instance and then this is most important step   climb your site so here we have to provide some  uh name what exactly you are looking in the url   so when i accessing the jira tool you have to  provide some url so what should the url contains
• 19:30 - 20:00 okay that url you have to specify here okay  so let me just show you what exactly it is so here uh just a second so let  me just give something called zera   uh demo by pawan so when i enter something which  will check which is already there or not now we   can just look at here this site is already taken  so we need to give something else okay so we need
• 20:00 - 20:30 to give something else so let me just uh okay  so we need to give something else so let me just   give some other name let us say uh instead  of jira demo by power and say jira training   now let us check whether it is available or  not yes now we can see which is available   so jira training by pawn so this is the name i'm  just using in the url and once it is available   you can see the green color tick mark and then  say agree so this will come under url okay jira
• 20:30 - 21:00 training bypass dot atlassian.net so this is  a complete url which you have to use later   so i say agree so once you said agree so which  will go and try to create a jira instance for you so it is trying to create
• 21:00 - 21:30 so it try you know it is still trying to  create yeah now we can see this particular   scheme you can just select some of the options  if you are required or else you can skip the   question not required and again you can skip  it so basically they are asking who are you   you are a founder or your product owner  your student or your business analyst   what you are exactly so they are asking here and  you can also skip this question not mandatory   so once you skip it then it is  going to create a new jira instance
• 21:30 - 22:00 so let it complete okay so now it is trying to create our jira  instance yeah so now the next step will start   so when you create a jira instance  right so multiple people in your team
• 22:00 - 22:30 can access the jira right so you need to add  different people in your team like including   product owner like developers tester scrum  master and these people will be part of the   jira project so they should be able to access  the jira tool so here you can specify those   email addresses so wherever is working on your  team in that particular project you can specify   the email addresses of them then automatically  these people will be added to the jira project
• 22:30 - 23:00 okay so we can do this step later also so once you  created the project then i will add the people to   that project so for now you can just keep it i say  continue okay so once you continue it is asking   like help us set up your jira so what exactly  it is i am you can select i am new to jira or   i am experienced with so you can just select  i am new to jira and my team is here you can   just select the second box my team is also new to  agile methodologies or my team is also experienced
• 23:00 - 23:30 with agile methodology you can select one of this  option i say new to it is just like a fill in the   bank's case okay i am new to jira and my team  is also new to hl methodologies and we spent   our time working on here in the drop down box  most of the times on what we are working feature   support operations and fixing bugs anything we  can select and i'm just selecting the features   or these are all things are optional guys okay  not mandatory required i just say skip it here   okay now we will see something called three  options you can just look at here okay this is
• 23:30 - 24:00 kamban project scrum project buck tracking project  so three different parts we have so we will work   on scrum project so which will manage the stories  tasks workflows for scrum team so for teams   sorry let's just go back again okay so we  need to select the middle project guys so   there are three options it is provided so we have  to select the middle one so again i'm skipping it
• 24:00 - 24:30 okay so if you have a team you have to provide  the email addresses or else you can just keep it   and you don't need to select this option just  keep it now this is the project which you have   to select the middle one so click on select  now here it is asking for project name so   what project we are going to do so we  have to provide the name of the project
• 24:30 - 25:00 so initially uh my project name is i'll  say opencart this is my project name   and once you proj once you specify your project  name it will automatically try to create one key   so what is key means so whenever you create a  story or whenever you create a task or whenever   you create a bug or test case whatever you do  whatever the object you are creating in the jira   so you have to provide some name to that so the  name is always followed by the prefix so that is
• 25:00 - 25:30 your key so for example when i create a new story  and the story contains some id let's say zero zero   one and which will automatically add this key  let's op underscore zero zero one okay similarly   if you add some task so task id will be there 0  02 is my task id so the task id will be created   by using this key let's say op underscore your  task id number so whatever object we created in   the agile process like it can be stored it can be  epic or it can be a bug or it can be task whatever
• 25:30 - 26:00 you created everything is called as an object  in the jira tool and these objects names will be   starting with key so that key we have to specify  here so by default it will suggest one key here   and you can change it let's say i say open card  i say oc i'm just saying oc you can change it   this is called key and this is the name of  my project and then i say create directly can   click on the create and once you have done this  which will automatically create a new project
• 26:00 - 26:30 in jira tool so now we can see this is  a home page of your jira tool so now   the jira instance is created for you and  this instance is managed with your gmail id   for 30 days and 10 people you can add into  this particular project so now we can just   click on this jira quick start and everything  we don't need this so now this is a uh the first
• 26:30 - 27:00 user interface of your jira tool and you can find  lot of things here your work projects if i just   go to the projects your project name by default  it will show you and if you have multiple projects   all the projects will show you in this list you  can select whichever project currently are working   and filters a dashboard just go to the dashboard  which will show you all your activities in the   dashboard and people here you can see the all the  team members information and apps means here if   you if you want to add any additional plugins into  jira like jfr plugin you can add it through apps
• 27:00 - 27:30 menu so there are multiple things are available  here and also this side you can see here this is   my project name and this is a board or scrum board  we can say roadmap backlog active sprints reports   issues components the lot of things are there we  will discuss later okay so this is a ui the front   you are the first ui of your jira application  okay so this is the way we need to configure
• 27:30 - 28:00 install jira tool okay so i will also provide the  screenshot step by step you guys can also follow   that because i already captured the screenshot for  this okay all right so now we have successfully   configure the cloud instance of jira tool  we have successfully configured cloud   instance of jira tool we are not downloaded  we have not installed anything we have just   configured the cloud instance of jira tool free  version 10 users 30 days okay so now we can work
• 28:00 - 28:30 with this tool 30 days you can practice it so  everybody can create their own instances of cloud   okay so after that so we have to know the workflow  so what exactly we can do in the jira tool so in   the previous session we have discussed about  what are the exactly scrum activities right the   same activities we are going to perform in the  jira tool so what are those activities so what
• 28:30 - 29:00 are the agile or scrum activities we do so let me  just list out here one by one we will try to do it   so we already installed and configure jira to so  now we are in the home page we are ready to do all   the activities so the first and most activity is  creating the project okay so creating the project   how to create a project in jira so at the  time of creating the instances itself we have   provided the project name right so that's the  reason by default you can see your project here
• 29:00 - 29:30 suppose tomorrow if i want to create a  new project in the jira then you can just   go to projects menu and you can select this  option you can just select the create project   and again you have to select what type of  project you want to select suppose here   classic project or next generation project and  say classic project and then click on the select   classic then again it will ask you the project  name it will generate the key and then create
• 29:30 - 30:00 so this particular flow we can use to create  a new projects for now i'm just closing this   because we already have a project that is a  project creation how to create a project in jira   and there is something called dashboard here if  i just go to the dashboards view all dashboards   and which will show you what are all different  projects we have and who's the owner access level   how many people are working on the project all  the information will be shown in the dashboards
• 30:00 - 30:30 so once we created everything it will show you  here these are the dashboards most of the time   management people will look at this particular  dashboards to know the status of the projects   okay and then how to create a project we have  seen and then the first and main activity is   their team works on the jira  right so team means what   scum master product owner developers tester so all  the team members should be part of this project   so the first and most important activities let us  see how we can add users or people to the project
• 30:30 - 31:00 or in jira okay there's a next activity so  first we have seen how to create a new project   and second thing is we need to add certain  number of people to that particular project   okay so now i'll show you how we can add users or  peoples into jira project so if i just click on   here again jira software we will go to home page  or this is my project name so can just click on
• 31:00 - 31:30 this which will go to home page so now we are in  the home page of jira software so how to create   a users or people in jira so create users for  this project what you can do is we have to go   to the settings here you can just look at here let  me increase the size also you can just look at a   small gear icon settings menu so in the settings  menu you have to just click on the settings here   and you can find something called user management
• 31:30 - 32:00 so by using this option what you can do is you  can add users groups and manage access request   so not only adding the people every people is  having every user is having different role like   one guy is acting as a product manager product  owner one gig is come master other is developers   testers multiple roles we have so let's go  to user management click on user management   and then it will automatically opens another tab  like we are entering into the administration part
• 32:00 - 32:30 and once you go to this particular screen so  here we have to add email addresses of the users   so and all working on this particular project  we have to provide the email addresses here   and currently if i just look at here i am only  the user for this particular project right so if   you want to add multiple users i can also add  those users let me go back again okay so here   we need to provide the email address so your team  members who are working on your team you can just
• 32:30 - 33:00 provide addresses of those email address let's say  i'm just using some dummy email addresses i'll say   abc okay he's a developer i said dev abc developer  i say prefix dev and uh i say some gmail.com   and some similarly i say some xyz and he's a qa  as a qa at gmail.com and similarly i say something
• 33:00 - 33:30 uh mno so he is a product owner i'll say pivo said  gmail.com so like this you can create multiple   users to this project okay and uh if i select this  checkbox what happens is these users can invite   a new users and access administrator and add  products and these are basically not administrator   users so i just don't want to select this checkbox  and say invite team members as soon as i click on   the team members and here you can use the real  gmail ids also guys if i add your email address
• 33:30 - 34:00 here you will automatically invite it to this jira  you guys can use my jira tool from your location   if i had your email addresses here okay so i can  just say invite team members and once you click   on that automatically the people will be added to  your project who is working under your team will   be added to this project so now it is added and  if i just come down here you can just look at here   so these are the different people i  have added to this particular project
• 34:00 - 34:30 okay so this is a basically user management  how to add users or people in jira tool   right so once we have done this then actual  workflow will start so in the scrum where exactly   we will start so first we need to start with  the backlog so we need to have product backlog   then we will have stories in the backlog we  have to create apix and first we need to have a
• 34:30 - 35:00 backlog right so in the backlog what you will have   we will have epics or each epic is having multiple  stories okay each epic is having stories and once   we have done this then we have to create a sprint  i have to create a sprint and we need to add   stories to the sprint we have to add stories  to the sprint and then we have to start sprint   we have to start the sprint and at the same  time once you start a sprint we need to add
• 35:00 - 35:30 tasks tasks for every story right so these  are the workflow step by step activity so   first we will see this first we need to  have a backlog then backlog contains what   backlog we will create the backlog product owner  will create the backlog by taking the requirement   from the customer right so first we need to have a  backlog for the project then the backlog contains   apic one or more number of apex then the ap  contains the stories right so let us try to
• 35:30 - 36:00 create this fast so let's go step by step so first  we will try to create a backlog and apic then i'll   come back to the stories how to create a backlog  inside the backlog we will have a epic inside   the epic we will create the stories now here uh  yesterday i have shown you one small document   guys so which contains all the epic stories and  everything right so let me just open the document
• 36:00 - 36:30 so let me just open the document yeah all right so here this is my product backlash  so yesterday class we have seen this so this   is my epic uh ap contains a multiple stories so  these are the stories and these are the titles of   our feature names and this is acceptance criteria  so let us try to create a peak and corresponding
• 36:30 - 37:00 stories in jira tool okay right so now let us go  to jira tool and here if i just go to your project   now i can just close this and this is our project  homepage right so if i just go here there is small   thing called backlog here you can just look at  here this is my backlog okay so if i just go   to the backlog click on this backlog right so you  can just look at uh two options versions and apex
• 37:00 - 37:30 versions and epics backlog we need to create  separately which is already there inside the   project okay so inside the backlogs we have  two options here versions and epics there is no   uh there are no stories or backlogs so far  we created this is completely empty now   it doesn't have anything if there is any  pixel storage which will show you here   okay so now inside the backlog when i click on  the backlog here which will show you this window   so here we have to create  something called versions
• 37:30 - 38:00 okay and then apex so first let's go to versions  okay once you click on the versions just a moment okay so show with uh versions panel use versions  to keep track and code release just a moment
• 38:00 - 38:30 as soon as when i click on that option which  will show you we need to add some versions there   let me click on once again so sometimes it will be very very  slow guys so we need to just keep   wait for few seconds and that will  automatically the menu will start   okay so select the backlog here  okay and then go to projects   and then select the project once again here so  select the backlog go to projects and select the
• 38:30 - 39:00 project what you want to work on which project you  want to work so click on project once again here   okay and then uh it will show you again go to  backlog once again yeah now we can see just select   the backlog go to projects and select whichever  project you are currently working then again   come back to the backlog then you will see these  options so under apex you will see versions and   issues and one more important thing in jira is in  every object we call it as a issue so don't think
• 39:00 - 39:30 issue is nothing but a bug so in jira language in  jira point of view every object which we call as a   issue so for example story is a one issue type and  similarly uh bug is an issue type task is also one   issue type right similarly a test case is also an  issue type so everything in jira each and every   object will consider as one issue type so what are  the issue types like story task epic so all these
• 39:30 - 40:00 things are comes under issue types in jira okay so  now if i just select the backlog and go to project   and select your project then automatically the  backlog items will come here so currently i don't   have any apics or stories now what you have to do  is first we need to create a apic so how to create   an epic so here select the apex and here you can  see versions and all issues currently i don't have   any versions or any apex so first we will  create a version so click on this create version
• 40:00 - 40:30 and under this project i'm just providing  some name to the epic okay so just a moment   let me just close these things first of all  so this is the initial screen guys okay when i   click on the versions versions information will  come when i click on the apex apex information   also will come so first of all let us try to add  version so i'm just clicking on the versions here
• 40:30 - 41:00 and then create a version so here i'm just giving  some version name okay i'll say this is open cart   open card open card version zero zero one i'm just  giving some number i say v001 open got v001 if you   want to write some description you can write it  and when this project start when the project is   end you can select the date so today i'm starting  and the whole project uh will end let's say
• 41:00 - 41:30 sorry i say february march 23 so two months  of time i'm giving and just say create   so now we can see the version is created  and then we need to go to apex and now we   need to add apex to this backlog okay now we  can just see a small link here create a pic   so i'm just clicking on the create epic  now you can see this is my project name   now here these are the issue types task story and  bug so these are the main three issue types we
• 41:30 - 42:00 have in jira guys task story and bug okay so what  kind of issue type we are creating now epic so we   have to select the epic here and then here we have  to provide the name of the epic and summary of the   epic so we can just look at the excel sheet we  have something called name of the epic summary   of the epic and what i can do is you can just  simply specify uh this is a name of the epic
• 42:00 - 42:30 this is a summary actually so  let me just type summary here   and provide a short name to identify the epic so  i can just give this as a name of the epic so this   is my name of the epic and this is a small  description of my epic or summary of my epic   similarly if you want to create another apex you  can just select this check mark automatically   create another and just automatically which will  give you another screen this epic will be created
• 42:30 - 43:00 and then another epic will be created and if you  have multiple epics you can just use this option   create another then it will automatically  give you another screen to add another epic   so currently i have only one epic under this  epic i will try to add multiple stories so   for now i'm just saying create so once you have  done this now you can see a new epic is created   so so far what have done under this project  we have created one version and also we have
• 43:00 - 43:30 created one epic so open cart underscore apex001  so this is a our apk and this is automatic one   id will be created oc and iphone one this is  a epic id which is created by jira tool itself   okay so if you want to see what our epics are  available inside the backlog just you select   your project here and then go to backlog and  then you can see what all apics you have here
• 43:30 - 44:00 and if you add one more epic that will come here  below this epic one more epic will come here   okay so this is where we need to  create an epic so inside the backlog   and we created one apex how to  create a backlog epic we have seen okay so we have to select  the backlog go to projects   select the project automatically these things will  come first create a version then create an epic   so once your epic is ready what is  epic epic is a collection of stories
• 44:00 - 44:30 so inside the epic we have to create multiple  stories right so that is the next activity   so once you created your backlog epic then we have  to create stories in jira and then we need to add   story points to them that is a fourth step so  once apk is ready we have to create a stories   under this epic and for every story we need  to add story points what is story part means
• 44:30 - 45:00 estimation rough estimation which we need to  define for that particular story so now i'll show   you how to add stories to this particular epic  story is a small requirement so now i'll show you   how to add the stories to this particular epic and  also we will add story points to that particular   story okay now as per our excel file so these are  the user stories right so now we have to create   these stories under the epic now let us see how  we can create them so go back and now to create
• 45:00 - 45:30 the stories under this epic what you have to do  is we have to directly go to create button here   okay if you click on the create button  you will see the project name and under   this is epic car which one you want to create  story you have to create so select the story   okay and once you selected the story here  we have to provide the summary of the story   here we have to provide the summary of the story
• 45:30 - 46:00 okay so how to provide the summary of the story is  just we need to copy from the excel sheet so let   me just copy here and this is a summary you can  say feature or title we can provide as a summary   and here if there is any documentation have  for this particular story to understand better   the product owner will attach those documents here  like ui screens or mock screens or dfd diagrams
• 46:00 - 46:30 if there is any any documents are available for  this particular story the product owner will   attach those documents to this particular story  okay that upload documentation is the option is   available here and then under description so in  the inside the description we have to add our   story so this is our user story which we need  to add copy this user story and specify here   and uh reporter so who is  creating the user story normally
• 46:30 - 47:00 here the product owner name automatic will come  if it is a product owner is doing this task   and reporter and then he's a reporter and if  i just look at here yeah it will come here   automatically so we have to select that reporter  name and if there are any link issues we can link   it or else you can leave it issues not required  and these things are not required and sne so whom   you are ascending the story so you have to select  that person who is responsible for that story you
• 47:00 - 47:30 have to select the proper user or is responsible  for the story currently i'm selecting myself   and then what is the priority of the particular  story so how much important it is how soon we   have to release this story to the customer  highest high low and lowest we have to select   and the labels you can give for every uh object  like you can provide the labels for stories tasks   epics everything because later the searching  point of view it will be very useful if you
• 47:30 - 48:00 want to search particular story or particular  task or whatever you can just search with the   label and then automatically the stories and tasks  will be displayed uh which are matching with the   label names if you want to provide you can  provide some label names or as leave it empty   and here the lib epic link so if i just select  this drop down which will show you the epic   which you have created so on for which epic  under which epic you are creating the story   so that epic we have to select here okay and  on which sprint you are planning this story
• 48:00 - 48:30 so currently we don't have created any  sprint we haven't created any spring   so currently you can just leave this as empty  so this is how we need to provide the details   in the story and then we just say create so again  if i just click on the create button it will just   create only single story and if you want to add  multiple stories then you can select this option   and then what happens when you create when you  click on this create then this story will be
• 48:30 - 49:00 created and again it will give you the same  screen once again which will allow you to add   one more story so let me show you that so select  this check mark and then say create now observe   this now this story has been successfully created  registration story is successfully created now   i want to add one more story so again the empty  screen is displayed here you can just look at here   right now i am just going to add one more story  so now the other story is a login is another story
• 49:00 - 49:30 i'm just summary and if there is any documentation  you can add it and then i am passing this one   user story description copy this  specify i say myself is reporter   and you don't need to modify anything here if  required and ap click is also automatically linked   i say again select this check mark because i have  one more story to add so i say create okay now it
• 49:30 - 50:00 is oc 0 iphone 3 login has been successfully  created now i am going to add one more story   so select the project select the issue type  as a story and then i'll provide the summary   and then a logo story i'm just going to add log  out and this is a responsibility of the product   owner so tester won't do this activity okay  so here am just copying the story description
• 50:00 - 50:30 put it here and then reporter linked  issues and you can just select assignee   and required information we can just put here  otherwise you can just leave it guys so sprint   we are not selecting here okay so later we  will add the storage to the spring so again   create another just say click create now  again one more story is being created logout   has been successfully created now i have one  more last story which i am going to create   user search products so provide the summary  and the description this is a user story
• 50:30 - 51:00 and the rest of the details as it is and  then this time i don't have any other stories   so this is my last story so i just  remove the check mark and then say create   so now totally four stories have been created now  we can just check the confirmation messages now   you can see as soon as i go to backlog and as  soon as you can see a pic and here you can see
• 51:00 - 51:30 what are the stories just now we created so one  two three four stories we have created under this   particular epic and every store is having some  unique id you can just look at here oc 0 2 oc 0 3   4 5 okay so there are multiple stories which  we have created under this epic so this is a   next step so for what we have done we have go to  backlog and we created epic along with the version   under this epic we created stories okay and  four stories we have created under this epic
• 51:30 - 52:00 how to create these stories go to create and  select that issue type as a story and provide   the description summary you can provide the  description and just create as many stories   you want you can just create them okay so  this is how we need to create all the stories   under the particular epic now once you created  your story we have to add story points because
• 52:00 - 52:30 we need to estimate that story and based upon  the estimation based upon the story point   we will select that story for the particular  sprint depends upon the duration okay so now   how we need to add story points to this particular  user stories now let me add some story points   so to add story points this particular  story what you can do is we can just   click on the story so here this is my story  registration so i'm just clicking on the story
• 52:30 - 53:00 so once you click on the story  another side you can just look at here   you can see story details i'm just clicking on the  registration observe this restation details are   appeared here story details are displayed here  when i select the login the login details are   displayed when i select the logout logout details  when i select the user search products user such   product details are displayed so now i need  to add story points to this particular stories
• 53:00 - 53:30 now first stories register as selected now if  i just look at here all the details will be   displayed along with the story points so here  we have to provide the story point number so   during the sprint planning meeting we will do all  these things so what is the story point for this   eight so i'm just giving the story point as eight  because these are very very important guys later   while calculating the metrics like when you're  generating the burnt down charts so these story
• 53:30 - 54:00 points time will be calculated so that's the  reason we must specify the story point number   for every story so story point once you  provide some number i say tick mark and   which is saved similarly for login story also  i'm trying to add story points so for login   for login five story points you can consider  them some companies one consider each   story point one story point equal to one hour or  some companies will consider like one story point
• 54:00 - 54:30 equal to six hours that means one uh one day so  five so the next story login story point is 5   and say tick mark so that is saved then log out  for log out ok so for log out the story point is 3   so i'm just going to provide story point as three  and then select and then for user search product
• 54:30 - 55:00 story point is i say five i say five and then  say tick mark so now we have added story points   for every story whatever stories we have added  into that particular epic we have added story   points okay so that's the next step so we have  created the number of stories inside the epic   and for each story we have added story points so  with this the backlog is ready so product backlog
• 55:00 - 55:30 is ready so backlog contains epic one ap currently  and the ip contains multiple stories along with   the story points so now the next step is we have  to create a sprint okay so in the agile process   in the during sprint planning  meeting we will decide so how many   stories we have in the backlog how many stories  we have to develop and test for that particular   sprint and what is the sprint duration we will  do that right so now as soon as we have ready
• 55:30 - 56:00 with the product backlog and stories are there  now the next step is we have to create a sprint   so we have to create a sprint and then  we have to add stories to the print   and then we have to start the sprint that's the  next activity fifth step and sixth and seventh   so now backlog is ready with that  which contains the number of stories   now the next step is we have to create a sprint  sprint is nothing but three two two four weeks of
• 56:00 - 56:30 time a small small period of time we can call it  as a sprint so once you create it as print then we   have to select some stories from backlog add those  stories to the particular sprint and then sprint   will start so as soon as we added stories to the  sprint developer and testers will add their tasks   for each story okay and then the sprint will  start now we'll see how we can create a sprint
• 56:30 - 57:00 then how to add the stories to the sprint  so the stories are already ready in the   product backlog which are created by the product  owner now we have to choose the particular stories   and add them to the sprint then we will start the  screen okay now let us see how to create a sprint   in jira so to create a sprint in jira what you  have to do is so if i just look at here we already   went to backlog and current project and backlog  click on the backlog can see the apex list and
• 57:00 - 57:30 stories everything here you can just close  this window also right so now we are ready   with the backlog so backlog contains  the epic ap contains the stories now   to develop and test these stories we should start  with a sprint right so now we need to create a   sprint so to create a sprint the first screen  and just click on the create sprint button you   can just look at here a small button is up here  create a sprint okay what is print sprint is a
• 57:30 - 58:00 a cycle which contains a two to four weeks of  duration within the duration we have to implement   few number of stories not all the stories  okay we will choose specific stories which are   uh enough to particular two to four weeks of  time like within two to four weeks our time how   many stories we are able to develop and test and  only those stories we will pick up and add them   to sprint and then we will continue the process  so let us create a sprint so i just clicking on
• 58:00 - 58:30 create sprint okay so once you click on  create sprint now observe this okay i'm also   closing this epic window and this versions  window yeah now as soon as i click on the   uh create sprint now you observe you  will see a new screen something like this   so this is a oc sprint one which is created now  it doesn't have any issues means what if this   print is empty now it doesn't have any stories  planned for this print as soon as i click on the
• 58:30 - 59:00 create sprint you will see this oc sprint one it  doesn't have any stories now what you have to do   from this backlog from this backlog we have to add  some stories into this particular sprint so now   as per the planning let us say developers and  testers decided to develop and test registration   login and logout functionalities as part of sprint  one then what you have to do is just we need to
• 59:00 - 59:30 drag the stories like this into sprint so first  story is added to the sprint one now similarly   login is also i'm dragging to the spring to one  and logout also i have planned for sprint one   now user search words i will take this story for  the another print later so now i have selected   few number of stories from the backlog into sprint  one okay so now these three stories are part of
• 59:30 - 60:00 sprint one so now currently three issues are there  in the sprint one what are those three issues   three stories registration is one story login and  log out okay so now our sprint is ready so sprint   is created and store is also added to the sprint  so once we have done this what is the next thing   we have created a sprint injeera added stories  to the screen down then we have to start the   sprint so how to start the screen there is  one option called here start sprint so once
• 60:00 - 60:30 you click on this starts print then the sprint  will start so when i click on the start sprint   you can just look at here so we need to specify  the duration very very important so this is a   sprint we have started first split how much how  much duration one to four weeks that depends on   the company okay so some people will take one to  two weeks or one to three weeks one to four weeks   max four weeks but it can also extend if you want  so i'll say two weeks duration and from which day
• 60:30 - 61:00 to which i have already selected two weeks here  so the end date automatically calculated okay   what is the sprint goal so to develop and test  registration registration login logout features   this is the goal of this particular sprint okay  because we have selected only three stories   for this particular sprint so once you  return the goal you can just come down
• 61:00 - 61:30 nothing is there so then just say start so as  soon as you start here the sprint is started   now this is a scrum board or we can say storyboard  so we can see the statuses everything in this   particular board and this is the active  sprint so currently which sprint is going   so sprint 1 is going if i just click on the  active sprints then what in which sprint you   are currently working on which will show you  here so currently all three stories have added
• 61:30 - 62:00 to the screen so to do and in progress and done  so still we have not started the stories as of now   so it is there in to do section now once it is  in progress we can just slowly move on like this   we can drag like once it is store is completed  then we have to move it to the done state   so normally these things will be done by the scrum  master guys okay during the scrum meetings they   will ask the different qa team okay what is the  status of the story and the developer says okay i
• 62:00 - 62:30 have done all the tasks for the story and tester  says i have done all tasks for this particular   story and then if it is in progress he will put  in in progress section or if it is completed   then you put the done state once it is moved to  the done state means what that story is ready   for demo the story is ready for demo and once the  product owner is accept or approve that demo then   we will release that as part of the feature so  this is how we need to track the statuses so now   we have just created one sprint added the stories  to the sprint now we have started the sprint
• 62:30 - 63:00 so started the split now once you started a sprint  each story is having different tasks suppose when   i say registration is my story or feature for  that registration story developer will do their   own activities tester also will do their own  activities right so for registration what are   the developer tasks normally what developer  will do is developer will perform these tasks
• 63:00 - 63:30 understanding the story or requirement design the  story coding the story unit testing integration   coding bug fixes team meetings these are all  different tasks done by the developer for that   particular story similarly as part of the qa you  will understand the story or requirement writing   the scenarios writing the test cases reviews  data preparation environment setup execution   box re-testing team meetings automation these are  all different tasks done by the tester for the
• 63:30 - 64:00 particular story so for each and every story there  are set of developer tasks there are some qa tasks   okay now we need to write these tasks inside the  story so now if i just go back for each story   we have to define developer will define their  own task tester will define their own task and   now from here this is a responsibility of testers  and developers guys so once this print is created   and started from there onwards developers  and tester responsibility will be the more
• 64:00 - 64:30 but during product backlog reading the stories  planning the stories these things will be part   of product owner responsibility of the product  owner scrum master once the sprint is created   committed stories then the responsibilities  developers and testers now before uh once you   started the pre-sprint one then what you have to  do is for every story developer will add the tasks
• 64:30 - 65:00 similarly for every story tester also will add  their own task and one more thing these stories   will be developed and tested by multiple people so  only one developer is not responsible for all the   stories similarly one tester is not responsible  for all the stories okay suppose let us say first   story one registration some group of developers  work one or two developers and one or two testers   similarly for every story there are multiple  developers and multiple testers working together
• 65:00 - 65:30 for that particular story now so before  progressing the story the first thing   is we have to clearly define the tasks for each  story we have to clearly define the task and we   will define the stars developers and testers  will define the task now let us see how we   can add task for this particular story now just  click on the registration once you click on this okay so or else what you can do is just a moment
• 65:30 - 66:00 if it is you need to just uh click on the  here you can just you can open got apix001   is there right so you just click on this which  will open up one small screen just a second it is responding very very slow guys just a second
• 66:00 - 66:30 so once you click on this it will open up  one small screen there you can specify the   task you can add the tasks for this particular  story okay let me just go to projects again   i'm just coming from the beginning so  go to project select your project yeah   now we can see you got the screen now so it is  come very late guys slowly we have to do so let   me show you once again so this is our scrum board  okay we have started sprint now we need to add
• 66:30 - 67:00 tasks for each story so let us take one  one story okay now i'll show you how we   can add tasks and everything so let us see first  story registration so click on this registration   okay once you click on the registration  story now you will see the screen   and in this butler screen you will see all the  details about the story okay now we can see the   description of the story and everything so now we  need to add tasks for this particular story so how   we can add tasks you can just look at here create  a sub task and when i say create subtask means
• 67:00 - 67:30 which will create a new task for this particular  story okay or in other way what you can do is   we can just directly go to create here and inside  the project you can select the task directly here   okay so select the task and now we can just  specify the summary and here you can just   select the something called on which epic and  which sprint you are going to add the task and
• 67:30 - 68:00 this is task is very high level task means it can  be anything not specific to story the task can   be anything not specific to story it can be any  meeting or it can be a review okay any task which   is not specific to that particular story right but  i want to create a task which is specific to story   okay now what i have to do is we need to call it  as a sub task so just click on the story then you   will see this window and here you can see one  option called create sub task so once you click
• 68:00 - 68:30 on the create sub task then sub task what are the  tasks you want to do so the first task as a tester   we need to add some task as a developer also  we need to add some tasks okay now let me add   first development task so as a developer what  you will do first so these are the different   activities we do so understand the requirement  design coding unit testing and everything so   let me add some tasks so first understand let's  say or we can simply directly i say understand
• 68:30 - 69:00 understand requirements is understand requirement   create and this is uh qa endeavor both the  job combinedly will do okay i say devo and   qa together will understand the requirements  create so now one task is created you can see   and somebody in the team we can just complete  the status task later so now another task i say
• 69:00 - 69:30 development or we can simply say design  design is one task and then development   development done by the developer and then  unit testing unit testing is done by the   developer and then what else they can  do unit testing and integration testing   integration testing and developer will do that  and also developer fix the bugs so bug fixing
• 69:30 - 70:00 bug fixing so these are all the different tasks  we'll add by the developers and similarly for the   same story we also add our qr tasks so just you  can just close this for now and once it is closed   so you can just close it then so developers define  their own task for this particular story now you   can just look at the scrum board see this this is  the registration story login story log out story
• 70:00 - 70:30 right so for registration story developers added  their own tasks understanding requirement design   development unit testing integration testing  bug fix right so now we need to add our own   task testing task we need to add so how  we can add again click on the same story   registration which will open up the windows  now these are the stories created by the   sorry these are the tasks created by the developer  so he is responsible for completing these tasks   and once the developer is completed these all  tasks and also testing tester tasks then only
• 70:30 - 71:00 we can say story is completed okay now let us add  few more tasks from the keyword side so click on   this plus button you can add or you can click on  this create subtask okay now qside so understand   the requirement day one queue is already  there so now test cases test cases creation creating test scenarios and test cases so this  is a one activity done by the qa so create
• 71:00 - 71:30 now one task is created and uh then after  testing cases what you will do is we will set up   environment and install bill this is another task   because it takes some few number of hours right  so each and every task we have to calculate guys   okay so because we will track each and every  activity in the hours so you need to even if you   do some one hour task you have to track that so  which will again automatically impacted your burn
• 71:30 - 72:00 down charts and reports so setting up environment  and installation of build and then finally   execute test cases test cases and then verifying  bugs verify bugs right so these are the qa tasks   so once we added all the development and qa tasks  to this particular story we can just close this so
• 72:00 - 72:30 developers and testers will do these tasks product  owner will not do this product owner just will   add the stories to the sprint once the sprint  is started that is again testers and developers   responsibility now we can just look at the scrum  board if i just look at this board sprint board   here for registration only we have added six  sub tasks just a moment let me increase the size   okay now for registration we have a six sub task  but rest of the stories so far we haven't added
• 72:30 - 73:00 any tasks so first we will see the entire flow for  registration then we will see rest of the stories   so for this particular sprint we have planned  three stories registration login and logout   for registration story we have added tasks  developer task and give a task okay so once   we added this now we need to progress so how we  need to progress so as soon as we have done this   registration suppose as a qa or dev we have done  this task for example or this task is in progress
• 73:00 - 73:30 then we have to move it into the progress slowly  we have to uh we have to drag it just a moment   so we cannot directly drag this  we can only drag the stories   not the tasks so what you have to do as soon as we  completed this story we have to just click on this   okay and uh there will be something called to  do you can see the status is to do right so if   you want to put as in progress you can just put  in progress okay and then say close now it is
• 73:30 - 74:00 automatically moved in progress section the task  is more to in progress right understanding and   once it is done once it is completed again  click on the same thing and you can change   the status so done so it's a close so now it is  moved to dance day so for this particular story   understanding requirement by demand qa is done so  we have moved it to the so one task is completed   for the story now development testing task will  go parallel right so what we can do development
• 74:00 - 74:30 uh design part so developer will completed the  design done okay now the design is completed   by the development now once the design is also  done development testing activities goal will go   parallely so both the tasks should be in the in  progress so how we can change it so development   is in progress now currently developers are  developing the software so we can put it in   progress and developer will update the status on  day-to-day basis now development is in progress
• 74:30 - 75:00 parallely our testing should also in progress as  per testing what you will do creating the tests in   our research scenario so tester will update this  tester what he will update in progress so once you   click on the in progress and then close it so  now you can just look at here development and   test scenarios and test cases from qsaid these two  tasks are in progress so scrum master will manage   all these things guys so come master every day  look at this particular scrum board and check how
• 75:00 - 75:30 people are working and how people are progressing  what are the tasks are in progress what how tasks   are completed or done so they will monitor it  okay if there is any delaying in scrum meeting or   scrum call they will discuss so once you added  all the tasks this is a developer and tester   responsibility to complete these tasks which  are created for the story so once all the tasks   are completed for this particular story then we  can say the story is completed the story is done
• 75:30 - 76:00 now let us assume let me complete all the tasks so  we can just say unit testing right so unit testing   click on the unit testing let's say developer  is done you can just you can also assign here   developer suppose uh at the time of adding the  stories itself we have to select the assignee here   so i said done so unit testing is also done  so integration testing so integration testing
• 76:00 - 76:30 is also as updating as a done and then  these are all q activities so let us see   development activities are done or not so bug  fixing is also developer activity so this is also   done so to complete the story first of all we need  to complete all the tasks which are associated   to that particular story and so development tasks  are done so now only keyword asks are pending   so now i am also progressing so you can update  in progress if i say which will go to the second
• 76:30 - 77:00 section so setup and environment installation  build is in progress and then again if i just   click on this i can just finish this you can say  done and close it so now it will go to done state   and creating the test scenario test case have  also completed so you can just say done and   say close and automatically go to done state and  two tasks are pending only executing verifying box   and test case execution is also completed then you  can say done or if it is in progress you can say
• 77:00 - 77:30 progress then what is the final task is pending is  development is also completed right so you can say   development is done move to done state so  all the tasks have completed except the   verify box so to close this particular story or  we can say to done for particular story all the   tasks should be completed so if i just look at  here again this is also should be closed done   so now we can just look at for this particular  story there are no tasks or pending so these
• 77:30 - 78:00 tasks will be updated on day-to-day basis based  upon your progress so now it is done everything is   moved to the done okay now finally what we can do  we can move the story to the done state that means   we can directly drag the story to the done  state or we can click on the move to done   you can see here click on this move to done then  automatically the story update parent issue not   required so here we can say done story i'm saying  so you can also look at here all the tasks are
• 78:00 - 78:30 cross here that means what all the tasks are  completed okay and then we say done so once   the tasks are completed then we can say the story  is done now you can see the story is crossed here   okay so restation cl story is completed once you  done all the tasks similarly the same thing will
• 78:30 - 79:00 be done for every story same thing will be done  for every story similarly once all the stories   are completed all the stories are in done state  then we can say within within the sprint duration   we have to complete this suppose if there is any  story which is not completed in that particular   sprint again that we will re-plan for the next  sprint okay we can add the same story for the   next spring if it is not completed or if there  are any bugs which are not fixed in the sprint one
• 79:00 - 79:30 those bugs also we can create as a task we can  add them into next sprint okay this is again   continuous process so once all the stories have  been completed first it will come to in progress   then it will come to done so once it is done  your cycle will be completed your sprint cycle   will be completed so now we can just look at  here registration is completed i say login   so login we need to add task first of all okay  without adding tasks without complete that
• 79:30 - 80:00 we don't do any activity on the story this is  called as a scrum board which will automatically   provided by the jira tool itself so what we have  seen so far is we have seen how to create a sprint   how to add user stories to the  screen we have started the sprint   and also we have added the sub tasks  also we have added the subtask and
• 80:00 - 80:30 added the sub tasks to the story and also we  have seen sprint cycle like to do in progress   done so each story will move on to the  different cycle so different stages   sorry stories stories within the sprint will move  to the first to do state then in progress then   done so to move the story one stage to another  story first we need to finish all the tasks   which are defined for that particular  story okay so these are the activities
• 80:30 - 81:00 we do finally suppose if we found any bug in the  particular story then how we can report the bug   then simply just go to the create and here  instead of story and task select the bug so   once you selected the bug this is a bug actually  so once you selected the bug just a moment right so create and this is the  project i'm going to create a bug   it should select actually okay just a moment
• 81:00 - 81:30 so let's open the project once again refresh the  page if something is not working sometimes it is   not responding properly all right so now you  can just go to create and uh here issue type   is story i'm just selecting the bug here sorry it  is not selecting actually it should select the bug this is a problem with the browser  see this it is not selecting the bug
• 81:30 - 82:00 task also nothing is selecting it's just  selecting only story okay so what we can do is one sec okay so here we are not able to  select any bug here because this is a   small problem with the application or ui it is  i think it is a problem with the ui a browser   so i'll show you this uh after few minutes in the  different way so this is how we can just uh do the
• 82:00 - 82:30 scrum activities okay because reporting the bug is  a again comes under the test cycle so that we will   see a separately so creating the sprint in jira  we have seen and added user stories to the sprint   starting sprint then we also added sub tasks  to the story and we have updated the status of   the stories and finally we completed the task for  that particular story and then we closed the story   this is all about sprint life cycle
• 82:30 - 83:00 okay so this is how we need to do the  scrum activities within the jira tool   okay so apart from this we also can do test  management activities like we can write it as   cases and we can create a test cycles we can  add the test cases to the particular cycles   we can upgrade the execution status we can report  the bugs so these things are comes under the test   management activities that is a next activity  test management activities but by default jira
• 83:00 - 83:30 will not provide you these options test management  activities to perform test management activities   so we have to install a special plugin called  jfire plugin okay so this is a new plugin which   we have to install to perform test management  activities okay so that we will see now so now let us start test management  activity so what are the test management
• 83:30 - 84:00 activities we do normally in the test management  activities we will write the test cases   okay or suppose you already written the  test cases in excel sheet or excel file   we can directly import all the test cases  into jira so we can write our own test cases   directly in jira or we can import the test  cases from jira so test cases we can write   and what else we create the test cycles so what  is the test cycle means the test cycle means we
• 84:00 - 84:30 can say regression test cycle or functional  test cycle or sanity test cycle so each cycle   we will add some number of test cases and we will  execute the test cases in that particular cycle   and then we report the bugs if there is any  mismatches between expected and actual so that   we should happen in the test cycle so creating  the test cases creating the test cycle and once   test cycle started we will execute the test cases  manually and then we will update the test cases
• 84:30 - 85:00 update test cases passed or failed or blocked  okay and after that we can see the we can also   report the bugs report the box and  then we can generate the reports   so these are the main activities we'll do as  part of test management right so now i will   show you how we can do these activities in jira  tool by using j fire plug-in so normally jira
• 85:00 - 85:30 don't provide any options to do this so we  have to install additional plugin called jfire   inside the jira then it is possible  okay now we can just look at here   go to the project and when you click on the create  here you will see only three types here story task   bug is task and epic nothing story task bug and  epic only four issue types you can see but if you   want to write the test cases and test cycles if  you want to create you have to see one more type
• 85:30 - 86:00 here that is called as a test so test the issue  type you have to see here along with the task bug   and epic but by default it is not appeared here  because so far we haven't installed j fire plugin   so now i am going to install jfr plugin and  then we will see one more task you will get here   so cancel it so how we can install uh  jfire plugin so to install jfi and plugin   first we need to go to apps section in the jira  tool there is a something called apps menu here
• 86:00 - 86:30 you can just look at go to apps and you can just  say find new apps click on this find a new app   so inside this find new  apps you have to search for jfire so once it displayed everything you  can search for jfi so these are the different   plugins which are supported in jira tool now  we are searching for jeff fire and once you
• 86:30 - 87:00 type jfi just press enter now we can see multiple  plugins so this is the first plugin which we have   to install so j fire for jira test management so  a flexible test management solution inside jira   perfect for agile teams focusing on the test  design execution and test automation and so on   so we have to just select this click on this so  once you click on that app or a plugin which will
• 87:00 - 87:30 go to another screen and this is a again free  for uh one month 30 days trial is there after   30 days which will expire okay this particular  plugin so now we can just click on try it free   and once you add this plugin so which will  show you all the information about this   then set start free trial click on start free  trial and then which is adding jfr plugin
• 87:30 - 88:00 into jira tool so once it is added successfully  then we can do test management activities   so once it is done you can just close this  so we can say we will tell you when you   app has been added you can just close this now it  is c it is trying to add the plugin into jira tool   so still it is in progress so once it is done  yeah now we can get the success message java for   jira test management was added so once  you have done this you can just go to
• 88:00 - 88:30 manage app click on manage app and which will  show you again all the different apps which are   installed in jira tool not required now just go  to jira software logo and it will go to home page   now observe this when you click on the jira  software here your project is showing click on   the project you will see the home page again now  observe this previously we don't have this option   jeffrey option we don't have previous now it  is added here that's the one change the next
• 88:30 - 89:00 thing is previously when i click on the  create we can see only task bug and epic   story test was not there now we got additionally  test option okay additionally we got the test   option so these two changes you will notice after  installing j fire plugin within the jira tool   okay so once you have done this then we can  do test management activities in jira tool
• 89:00 - 89:30 okay now let me do you how we can do this quickly  very simple and very easy also so first let me   show you how to write the test cases so to write  the test cases first we need to go to gfr here   so these are all options which are available for  agile or scrum process but if you want to do the   test management activities we need to click on  j fire option here click on j file then it will   give you few more options and there are multiple  sections are there so you can just look at design   section planning and execution and reporting and  then integrations there are multiple sections are
• 89:30 - 90:00 there and design section mainly we create a test  case and bdd type of test case and we can search   the test which we have already written and if  you have test case in some excel file or some   other sources we can import those test cases so  these things we can do as part of design path and   planning and execution we can create a test cycles  we can execute our test cases and we can also   update the status are passed or failed so these  things we can do as part of planning and execution
• 90:00 - 90:30 and after execution is completed we can see  the reports test summary report test metrics   traceability matrix so these things we can see  as part of reporting okay these are the things   as possible through jeffer plugin so now  i'll quickly show you how to write the   test cases and uh two ways we  can do this guys one thing is   we can directly write the test case in jira that  is one thing or if you have written multiple test   cases which are already there in excel file you  can import those test cases in jira you can import
• 90:30 - 91:00 those test cases in jira so i will show you both  the ways okay so what we can do is go to jira tool   okay so how to create the test cases so click  on the create test so how we have to navigate   here from the main home page click on jeff fire  plugin then you can see create test so click on   the create test and then you will get one more  screen like this inside this this is a project
• 91:00 - 91:30 name and issue type is a test issue type is a test  by default selected now here we have to provide   the test summary okay let me add one small test  case so here i have few test cases okay now let   me add one test case or we can also add open cut  test cases which we have already created earlier   so let me add one small test case here some  sample test case for i say registration
• 91:30 - 92:00 or we can say register user this is summary  or you can just copy this summary as it is okay or else i will upload those test cases later  so first i will try to show you a small test case   how to write the test case okay so here the  summary is i say login to test case later   if you want you can delete this no problem so log  into test case so log to application so this is my   summary of the test case and if you have any  document which is required to understand the
• 92:00 - 92:30 test case you can upload and you can write the  description so login to application this small   description you can provide and then whatever  the information you want to add you can add   like assignee who is responsible for executing  this case and on for which epic you are creating   and on which sprint you are planning you can  just specify that active sprint or future print   so you can also update these details later so  for now just create a new test case like this
• 92:30 - 93:00 so but test case means what we need to provide the  actions and expert results and everything right   but this one doesn't have anything so where we  have to update them so we will update in the   next screen so after filling the details basic  details summary and description and everything   then we have to click on create so once you click  on the create then the test case is created just   we need to click on this issue link so your issue  has been created but it's not currently visible
• 93:00 - 93:30 you can just click here or after few seconds it  will disappear but where you can see the test   case which is created you have to go to search  test okay click on the search test then here   you can see whatever test case you created so this  is a test case just now we created but we haven't   provided any actions expected result priorities  and everything right so now we need to add them   so where we can add just click on this test case  link now it will show you this particular screen
• 93:30 - 94:00 and here you can find multiple options here  attachment create a sub task link and differ   actions and test details and test executions  and so on multiple options are displayed   so now we need to add steps and expected results  to this particular test case now how we can add   it if you want to add it what we can do is we just  go to details test details icon we have to click   so once you click on test details i icon then  you can see the small form test details form
• 94:00 - 94:30 right so here you have to provide  the test step data test result   okay what step you have to perform what data i  have to use what is the result we are expecting   so these three things we have to add so first let  me write one step so here open application url   okay what's the test data we use ww dot open and  test results what you are expecting app url open
• 94:30 - 95:00 and able to see able to see home page this  is our expected able to see home page the   first step then after completion of the first  step click on the tick mark then we can add   one more step see this one step is added and the  second step so what is the second step to login
• 95:00 - 95:30 so here provide valid username username  and password and what is the data here   valid user and password and what is the expected  what is expected uh provide valid username and   password value user and password what is expected  here text fields text fields should allow
• 95:30 - 96:00 values okay done so next step is  done after completion of this step   again we have to click on the tick mark then  one step is added so two steps added so far now   third step so after providing username password  then what you have to we have to click on submit   you can click on submit button and then no data  not required not applicable and user should
• 96:00 - 96:30 go to my account page so this is our expected  result and this is my last step so we can just   click on this done so another step you don't  need you can just click on the cross mark   or let it be there so three steps we have  added test data test results and everything   apart from this we can also add some other  information and any comments if you have history   working log so all these things we can update  if we required or else we can leave it empty
• 96:30 - 97:00 so this is how we need to create a test  case now i have created one test case   manually in jira tool but again this is a little  difficult thing guys because if you have 100 test   cases if you want to do this like this 100  times it is very very difficult task right   so normally what you will do in the beginning  levels we will write all the test cases in the   excel sheet or excel file so we will conduct  multiple reviews once you approve your test   cases then we will upload all the test cases  and one shot instead of writing multiple test
• 97:00 - 97:30 cases like this we will import all the test cases  into jira at one chart okay now i'll show you how   we can do that import also so once you created  your test case where you can see the test cases   in where exactly in which place you can  see the test cases first go to the project   and you will see the project home page we need to  first go to jfr plugin and here inside the jfire   okay you can see the search test and inside  the search test you can see the test case
• 97:30 - 98:00 and once you click on the test case once you click  on the test case and then you can see the details so these are the details yeah now we can see the all the steps and  everything so if you want to execute the test   case then we can go to execute so test execution  so this option we will use later once we added   these test cases to the test cycle then we  will do that okay so this is the way we can
• 98:00 - 98:30 create test case manually in jira suppose i don't  want to do like this i want to import bulk number   of test cases into zero at one shot okay then  how we can do that so now i'm going to show you   the next thing is how to import the test  cases so far uh we have seen two things so how to install jfr plugin and also  we added issue type test to the project
• 98:30 - 99:00 i show we have we have seen like this is not  required and then we have seen how to create a   test case in jira manually right so now i'm going  to show you how to import multiple test cases into xero tool so now i have already test cases  written in my excel file so i want to import them
• 99:00 - 99:30 into xero tool so how we can do that so to do this  we need to follow certain prerequisites guys okay   so we have to write the test cases in excel  by using proper template because in our excel   file in our test cases the headings will  be different and as per jira perspective   the headings will be different so we need to be  sync in both like excel sheet whatever headings   we are using in which format we are using  excel file that should exactly match with   the jira format and then only we can import okay  so here i have created a few number of test cases
• 99:30 - 100:00 according to jira template or jira format so  here the main you can add any number of fields   but you need to map later so here i have written  few number of fields let's say test case names   test case description and these are the steps  for one test case these are the tested data   for each step test results and labels if  you require you can update the labels also
• 100:00 - 100:30 okay so this is one test case still here and this  is another test case so totally two test cases i   have register a register user user login so let us  say i have n number of test cases like this i want   to import all the test cases in my jira so how we  can import them instead of writing each and every   step i can import all the test cases in one shot  so let's see how we can do that so we have login   to application already there so let me try to  delete this test case because i'm just going to
• 100:30 - 101:00 import now so i'm just deleting the test case so  now i don't have any test cases now we just go to   search issues right so not here  we need to go back to the project and here go to j fire inside the j fire we have  to search for issues go to the j fire click on   the j fire and then you can see search test in the  search test i don't have any test cases everything
• 101:00 - 101:30 is empty okay now i want to import the test  cases so to import the test cases make sure   your excel file or x your test case template  should exactly match with jira template okay so   this is the format exactly jira will follow so now  let us try to import these test cases in jira tool   so how we can do that so here you can see  some functionality called import again go back
• 101:30 - 102:00 go back to jira sorry go back to our project and everything we can do only within the j5  plugin so select the j fire here so here you have   to select something called import test you can see  here this is import test click on this import test   and once you have done this you have to do some  flow here i'll show you so we can just close this
• 102:00 - 102:30 all okay so once you click on the import test so  here we have to choose the excel file so this is   the excel file which i am going to import this  is the excel file which i am going to import two   test cases register user user login so close this  excel file before so here i am browsing the file   click on the choose file i am selecting the excel  file open so now it is trying to get that file
• 102:30 - 103:00 okay once it is done and you can  just click on the next it is success   then click on the next and here in the excel file  in excel sheet the first row is a heading part   right so we have to start from the second  so instead of one we have to say two here   okay and then delemiter if i discriminator you can  just look at here in the excel sheet how the test   cases recognize how we can recognize the test  cases are different so one test case to under
• 103:00 - 103:30 test case is there any discriminator there so  based on the test case name change suppose if   there is an empty row between one test case  another test case you have to select md row   or if you are using id so you can use id change  so multiple options are available so currently the   test case name is a different so consistent  test case name so if i just look at again   uh jira test cases see this here the test case  name is here and what's the next test case where
• 103:30 - 104:00 it start again with the test case name so test  case name is a discriminator similarly i selected   this and import all the sheets or import selector  sheet if you have multiple sheets in your excel   you can select first one if you want  to select if you want to import only   test case from specific sheet then select the  second one import selected sheets and here we   have to provide the name of the sheet  so let me check the name of the sheet
• 104:00 - 104:30 so test cases this is the name of the sheet so i  just writing them test cases okay and then click   on next so once you click on the next it will try  to import the excel sheet which contains all the   test cases yeah so now this is the very very most  important step so here so these are the actual   jira fields for every test case there will be  assignee comments component description epic link   externally there are a lot of things are there for  every test case but in our excel template we have
• 104:30 - 105:00 to map these fields with our excel template for  example in excel what are the headings we have   so we have description so just select the drop  down and these are the feeds which we have written   in our excel sheet so we need to exactly map with  that so description is available in our excel   so we need to select the test case description  and what else we have in excel file so we have   a name also so tc name test case name we can  map and then what else we have we have a steps
• 105:00 - 105:30 so steps we can map with the test step and  test data is also there so test data we can map   so like this whatever fields or columns we have  in excel field excel file so we need to map all   the columns with the jira fields okay so once the  mapping is done right so then you can say next and   do we have anything result is also we have right  so expect a result so test results also we can map
• 105:30 - 106:00 that's it so whatever the columns we have written  in the excel the same fields we need to map it   here and then next done so once you click on the  next so just validate here because every mapping   whatever we have done is correct or not if you  want to validate you can just click on validate   and if mapping is perfectly done so which is  success so two issues will be created successfully   and then we can just begin import click on begin  import so once you click on begin import now your
• 106:00 - 106:30 test cases are importing so previously we don't  have any test cases now i'm trying to import   two test cases so now let it complete yeah now two  issues have been imported successfully and again   if you want to import few more test cases again  go begin another input again process will start   okay this is the workflow of importing excel  setup settings mapping validation and then import   so now where you can see the test cases which  are imported just again go to search tests then
• 106:30 - 107:00 here you will be able to see the two test cases so  now let me open the login click on the login now   you see the description and also you will see the  steps go to the details here click on the details   now you can see all the steps have been  successfully created five steps we have in   the test case similarly register user so go to the  details and here all the steps have been created
• 107:00 - 107:30 okay so this is how we can import  multiple test cases from excel to jira   so this is very very useful option and  this is the way we can do most of the times   we don't write individual test cases manually  takes a lot of time so instead because initially   we will start with excel file so once all the  reviews are completed finally we will import   all the test cases from excel to zero tool okay  done so this is how we need to import multiple
• 107:30 - 108:00 test cases in jira tool so this is the first  initial task we do so we have created test cases   manually or we can import the test cases into  jira tool okay and the next and final action is   we have to create the test cycles we have to add  test cases to the cycles then we have to execute   reports and traceability matrix there  are few options which we have to do   okay so creating the test cycle so we have just  created the test cases right but where exactly we
• 108:00 - 108:30 have to execute them so we have to execute those  test cases while creating a cycle test cycle   within the sprint okay within the sprint itself  we will get multiple bills from the developer   right so for each build we will create a  new cycle and the set of test cases we will   add to that particular cycle and then we will  execute it okay so now i will show you how to   create a cycle how to add the test cases to  the cycle then how to execute or update the
• 108:30 - 109:00 status of the test cases and then finally  we will see the reports so let's go back   now we are done with the test cases now again  go back to the uh jfi plugin go to our projects and click on the j fire okay once you click on the j fire it will show  you all the options yeah so now come to the next
• 109:00 - 109:30 section planning and execution so cycle summary  search test execution manage execution filters   the multiple options are there so here we have  to go to cycle summary to create a new cycle   so cycle summary so in the cycle summary we have  to create a new cycle okay now if i just look at   here by default there are cycles are created so  unscheduled cycle ad hoc by default will be there
• 109:30 - 110:00 and apart from this this with the project version  which is also already created one cycle here   okay so if you want to create a new cycle  just click on the create a new test cycle   okay so here version number is unscheduled so we  have to select the version number opening card   version 0 0 1 then cycle so we can just give a  cycle name so here i name it as my or you can say   regression cycle okay regression cycle and then  you can specify the bill number or environment on
• 110:00 - 110:30 which environment you are executing and from  date which day to which day you are going to   execute this cycle you can spell select all the  details of the cycle and then say save so now   cycle is created new test cycle is created so now  we need to add test cases to this particular cycle   so what are the test cases we are going to execute  as part of the test as part of the cycle okay
• 110:30 - 111:00 so for that what you can do is you can  do two ways either you can just open   the cycle like this regression cycle and  you can just add test directly from here   or else we can go to the test cases individual  test cases and we will update the cycle also   okay suppose if you go to the  test case let me go back again search test cases there are two ways we can do  suppose i want to add this login test case to the
• 111:00 - 111:30 regression cycle so select the test case here  and you will see the cycle also somewhere priority label okay so here you can just say  execution so test execution   or actions test execution just go to this test  executions okay and here you can see something okay not execution
• 111:30 - 112:00 actions yeah so we can just go to actions first  icon and then you can see add to test cycles so   in which cycle you want to add the test case you  can just click on this button add to test cycle   and then you can select the which  cycle you want to add this test case   so individual test cases we can select  which we can add to the cycle so this is   the one option we have so the other option is  we can directly go to the cycle let me go back
• 112:00 - 112:30 so go to the cycle summary which will show  you the which cycle we have just created   so if i just look at here so regression cycle  which is created so now if i want to add the   test cases to the cycle click on add tests here  and here we need to add so we have to write the
• 112:30 - 113:00 uh test case names here user login register login  so user login i'm adding and then register also   i'm adding and who is responsible to execute this  test cases you have to specify it i'm just giving   as a some name word is ascend we have to give  it that name so it just specify and then say add   so once you added this those test cases will be  added to particular cycle okay once i added the
• 113:00 - 113:30 test cases to the cycle then we have to execute  our test cases as part of the cycle so now i'll   show you how to execute and update the status  that's the next thing so added test cases to   the cycle now we are going to execute and update  the statuses so to execute the test cases what   you have to do is we have to first go to the  cycle summary okay and also you can just go to   test search test executions the second option  is available so go to search test executions
• 113:30 - 114:00 under search test executions you can see the what  are all test cases are ready for execution here   for this particular cycle okay so from here  we can update the status so for example this   particular cycle regression cycle these are  the test cases are planned so still unexecuted   we have not executed this okay so need you  need to execute these test cases manually   there may be pass or fail whatever it is we need  to update the status so how to update the status
• 114:00 - 114:30 click on this test case okay let us say  register user click on the test case and once you open the test case and there is an  option called e small test execution okay so you   need to just click on this e once you click on  the e icon then here you will be able to update   one second okay just a moment somewhere you can  see the option yeah here you can see so this is
• 114:30 - 115:00 the test case unexecuted unexecuted so far so  now we need to execute so let me just make it   as a pass or you can also make execution of step  by step okay just a moment so to execute the test   case we can do here directly or we can also do  in some other way i'll show you just a moment
• 115:00 - 115:30 so first of all open the  test case go to the details   don't directly go to execution go to the details  okay so once you go to the details one sec so these are the steps right  you can see these steps
• 115:30 - 116:00 just a moment okay so here i think there is another way  to do this but it is not showing anywhere   we can make the test case past or fail even  step level also we can do that so somewhere   i could not see that option okay so we'll see that  later so for now i'm just using this option so   just come down so this is a test case and which  is not executed so i'm just passing it from now
• 116:00 - 116:30 okay past success and similarly  just go back again test cycle   once it is passed then go back to your test cycle okay so now we can just look at here two test  cases one test case got passed we have executed   so similarly i'll make one testcase.fail so  click on the test case once again here user login
• 116:30 - 117:00 okay and here again i want to   make this test cases passed or failed so you  can just go here and i make it as a fail so my   test case got failed so manually how to execute  okay execute accordingly you have to update the   status here so once it is fail everything is  done so once it is done go to again go back
• 117:00 - 117:30 right so once you go back now you can  see the execution status so one is got   failed one is got passed so now we need  to report the failure test case as a bug   right so then you can just go to create and  here instead of test you have to select the back   okay now bug is selected now you have to write the  summary so login failed with varied credentials
• 117:30 - 118:00 right so we need to write all the steps for  login right you need to write all the steps here   and then developer name so he is a reporter  and fixed versions so in which version you   want to fix so these details automatically  populate guys okay your project will be   set up in the jira before itself so all the  versions everything will be populated and priority   and as per the jira by default it will show you  only priority but if you want to get the cvrt we
• 118:00 - 118:30 need to add some customized options so though  customized options will be added by the admin   so you guys can also select the priority as well  as crt and on which environment you have executed   the test cases and screenshots you can attach  here and in which version these bugs are effective   so all these things you have to specify  any so we use a responsible for fixing   this issue we have to select the developer  name like this and on which epic you got   this issue you have to select on which sprint  you got this issue you can select the sprint
• 118:30 - 119:00 so all these things you have to select and then  create so this is how we need to rise a bug so now   you can see bug is rise if i just go and click  on this link you can see the bug information so this is all about bug details so once the  developer is start working on that bug they   will update the status and they will also write  the comments here whether it is fixed or it is in   progress and how the what is the status of the bug  and accordingly we have to re-verify and close it
• 119:00 - 119:30 and if you want to see all the bugs list  where you can see is we can just go back to   the project again and here you can just look at  the issues right if i just click on the issues   you will see all kinds of issues so including  stories tasks bugs everything you can see here   okay whichever you want to click here that  details will be displayed at the right side   so this is all about bug reporting so whenever you  find a test case got fail you can report the bug
• 119:30 - 120:00 so we also seen a reporting box and finally  we can also see the reports so agile reports   will be different guys in agile we will see  burn down charts and everything i will show   you that first and then we'll come back to the  test summary reports again go to the project okay and then select the project right so here  you can see the something called reports okay
• 120:00 - 120:30 in the project dashboard you can see  the reports so click on the reports   and these are all agent reports guys so not a  test case reports now you can see there are so   many charts are available so burn down chart  burn up chart sprint report velocity chart   cumulative flow diagram so these are all the  metrics which will be taken care by the scrum   master so scrum hashtag has to know how we can  calculate these metrics and how we can check the
• 120:30 - 121:00 efforts of the team and you can just click  on each and every chart here burn down   burn down chart so this is the chart which is  basically burn down basically the main information   which will display is how much we have planned how  much we have completed still how much is pending   okay so how much how much story points we have  given how much we uh how much story points we have   expended on the or spend on the  particular story so those details   will be displayed in the burn down charts  and each and every story level task level
• 121:00 - 121:30 everything will be displayed so burn down chart  sprint report so this is against print report and   velocity chart so these are all automatically  displayed in the jira tool somehow it is not   displayed because if it doesn't have proper  data which will not display so version report   epic report control chart so there are a lot of  things are there guys which will taken care by the   scrum master so he's the main role okay he is  basically driving the process and facilitating the
• 121:30 - 122:00 agile he will monitor everything so these are all  the agile related reports but whatever what about   the test summary reports we need to go to j fire  plugin again go to project and here there is a   project called jfi right so jeff all the test  related activities we can see only in the jfire   okay because that is the additional plugin through  which we have done that so in the jfr plugin you   can see uh reporting test summary test matrix  traceability matrix i just go to test summary
• 122:00 - 122:30 test summary which will  give you test summary report okay so you can see here total test we have  created two two are executed okay and uh   everything labels if there are any labels  so labels will be displayed if there are any   components components will be displayed  so schedule cycle unscheduled sidekill
• 122:30 - 123:00 will be displayed here so this is a  test summary report and test matrix so we go to test matrix which will display the  test matrix also how many are failed how many   are passed in the graphical format okay which  will show you that this is the one type of test   summary report then traceability matrix these  are the three important reports we will have   for testing and agile reports and graphs will  be taken care by the scrum master we don't need
• 123:00 - 123:30 to bother about but at least we need to know  what are the different drafts will be created   in agile process in interview people may ask you  so these are the different traceability matrix   okay so what are the requirements we have and what  the test we have created executions level defects   so everything will be displayed here so we have  to select the proper we need to have proper data   and we have to map them correctly and  then only the report will be accurate   right if there is any uh mismatching or not  mapping is done like sprint is different test
• 123:30 - 124:00 case or different cycle so then report will not  be accurate so if you provide all the data test   cases cycles everything properly then your reports  will be accurate okay and you can also filter this how many uh all types are version what is the  different versions cycles and if there are any   folders within the cycles we can select the  folder level and execution status how many   are passed how many failed so this kind of  information we can see that okay so these are
• 124:00 - 124:30 the tasks also we have completed earlier as part  of a jn right so that also will be displayed here   so these are the three important uh reportings are  there in jira especially for test management side   and uh charts which are again belongs to agent  burn down burn down charts velocity charts   so they will take care of our scrum master  so they will analyze the report and they will   check the health of the agile like how the process  is going on what are the blockers how much extra
• 124:30 - 125:00 time is needed so those things will be analyzed by  the scrum master by seeing those reports and here   the test reports we will taken care by us even  our management leads will look at these reports   how our testing is progressed okay so these things  are available and additionally there are some   options are provided integrations suppose your  test cases are automated through selenium or   some postman tool or some other api test cases  you can also integrate those tools with the jira
• 125:00 - 125:30 so you can also execute test cases automation  test cases in selenium and the status we can see   in jira also so for that some apis are provided  here some options integration options are provided   within the jira so by using these options we can  also integrate jira with some third-party tools   so that kind of facility which is already there  in jira by using jfr plugin which is unpossible   okay otherwise we cannot do this so these  are all different options are available
• 125:30 - 126:00 very high level and day-to-day basis we almost  work with these options as a test engineer because   different people will involve in the project and  different people are having different roles so   according to those roles permissions will be given  and according to those roles they will create the   stories or some people will create the story  some people will add the tasks some people will   track the status some people will move the  stories from one place to another face some   people will work on the reports so depends upon  the privileges or permissions you will work on the
• 126:00 - 126:30 jira tool okay so this is all about zera test  management tool so these are all test management   activities and these are all scrum related  activities we can do using single tool so   that's the beauty of jira so in single place we  can do everything but if i don't use jira we have   to use multiple tools like for agile we use some  tool but test management we use some tool for   backtracking we use another tools instead of using  multiple tools we can do everything in one place
• 126:30 - 127:00 so that's the reason jira becomes very  popular so this is all about jira tool   okay so jira is agile test management tool so  we are using cloud instance so we can work with   this instance almost 30 days and every option  you can try with that so i'll share a small   document so i have taken the screenshot of almost  every activity what we have done in the jira
• 127:00 - 127:30 so go through this document and practice each and  every option which have explained in the session   okay everything is there but test management  activities i have not captured the screenshot here   and you guys can go through the video parallelly  you can do the tasks okay till bug reporting   spring cycle creation adding the stories to the  sprint all of them so creating the test cases   importing the test case i already shown you in the  video so you guys can watch this video once again
• 127:30 - 128:00 and then do these things okay so that is  all about zera tool how we need to automate   agent activities or test management activities in  jira told us okay so that's all for this session