Skip to main content

JIRA - Introduction

Why Need JIRA?
For better Project Management and Issue tracking, We need a tool which can fulfill bellow given requirements.
  • Manager can create new software project.
  • User can describe information and additional points which are discussed with team regarding software project.
  • User can maintain and track progress of software project.
  • User can track what types of issues have been faced during the development phase.
  • User can track what type of issues have been Posted by Software QA team.
  • What are the enhancements and changes have been done during the Process.
  • Whole Team can be aware of all the communications.
  • Managing person can assign the tasks to team members for managing Project.
  • User can search tasks, Issues etc..
  • Team can give their feedback for more improvements.
  • Reports for the all the procedure should be created.
Above listed functionality has been satisfied by JIRA Project Management software which we are going to learn. We will learn how JIRA can manage everything, how we can use this tool properly this all query will be solved soon.


What is JIRA?

  • JIRA is a software tool which has been developed by Australian company. This tool is used for Bug tracking, Issue tracking and Project Management. It allows you to assign, prioritize, report and audit your 'Issues' of a Project or change request.
  • It is extensible platform as it is customize different units and work flow of a project by using Agile methodology.
  • It improves productivity by saving time and improves quality by ensuring all task information and follow-ups till the completion of a project.

Project
As per the image we can consider that First a Project have been created from JIRA tool and then all other Procedure will take place. Projects have their different Components like one application is developed in web and integrated with android device. And If any changes will be required for improvement of developed project then it can be divide in different Version.

Issues

There are much different type of issues which we can post it on jira. We can Prioritize issue in  Low level , Medium Level , High level and critical Level. Thus, basically we can say that the  Project can be combination of many issues.

Work Flow

JIRA followed agile model for working. As agile have feature like we can fix the bug in the  middle of the development so it will quite good then waterfall model. Thus, JIRA followed this  methodology. Here is the example of JIRA work flow,

  • Open is the status of the issue which indicates that issue have been found in project.
  • When developer start to solved it then it status changed in to 'In progress'
  • if issues is solved then it will have 'Resolved' status and if it marked as solved but actually some problem is still occurred due to the same issue then it will have status as 'Reopened'.
  • Once an issue have been solved properly then it will have status as 'Closed'.

Comments

Popular posts from this blog

JMeter Exceeded Maximum Number of Redirects Error Solution

While running performance test, JMeter allows maximum 5 redirects by default. However, if your system demands more than 5 redirects, it may result in JMeter exceeded maximum number of redirects error. In this post, we have listed down steps to overcome this error. Actual error in JMeter: Response code: “Non HTTP response code: java.io.IOException” Response message: “Non HTTP response message: Exceeded maximum number of redirects: 5” This error is noticed because  JMeter  allows maximum 5 redirects by default and your system may be using more than 5 redirects. You need to increase this count to more than 5 in jmeter.properties file. Follow below steps to achieve this. Navigate to /bin directory of your JMeter installation. Locate jmeter.properties file and open it in any editor. Search for “httpsampler.max_redirects” property in opened file. Uncomment the above property by removing # before it. Change to value to more than 5 Eg. 20. Save the file and restart JMeter. If

SSO with SAML login scenario in JMeter

SAML(Security Assertion Markup Language) is increasingly being used to perform single sign-on(SSO) operations. As WikiPedia puts it, SAML is an XML-based open standard data format for exchanging authentication and authorization data between parties, in particular, between an identity provider and a service provider. With the rise in use of SAML in web applications, we may need to handle this in JMeter. This step-by-step tutorial shows SAML JMeter scenario to perform login operation. First request from JMeter is a GET request to fetch Login page. We need to fetch two values ‘SAMLRequest’ and ‘RelayState’ from the Login page response data. We can do this by using  Regular Expression Extractor . These two values need to be sent in POST request to service provider. Refer below image to see how to do this. We will get an HTML login page as a response to the request sent in 1st step. We need to fetch values of some hidden elements to pass it in the next request. We can do this b

A Tutorial to Send Email using JMeter

Sending email is a mundane activity in any professional’s life. It’s a common medium for communication nowadays. Therefore performance testing of email server is not only important but necessary for an organization. JMeter can be helpful to perform load testing in such scenarios. In this tutorial, we will see how JMeter can be used to send email. We will use SMTP Sampler of JMeter to send an email. JavaMail API is needed to enable email functionality in JMeter. Download it from  here  and paste the jar in JMeter’s lib folder. Now, perform below steps to configure SMTP Sampler. Add a new Thread Group under Test Plan. Right click on Thread Group and select Add–>Sampler–>SMTP Sampler. We need to populate SMTP server’s details in this sampler. We will use GMail for sending an email. For this, enter these values in SMTP Sampler fields. Server: smtp.googlemail.com, Port: 587. Provide values in Email Address From and To fields of Mail Settings section to specify sender and reci