How to configure Jira Effectively

Importance of Jira:


                   JIRA is an issue management platform that allows teams to easily manage their issues throughout their entire lifecycle. It is highly customizable, and can be tailored to fit any workflow you need. It is primarily used in software development as a way to manage and track development efforts.

JIRA provide grouped documentation i.e. multiple task can be grouped by assigning versions and due dates. All the document that is being entered by any of the team member can be seen through this would become easier to get those documents and can be use where ever needed. And it can also define any task with their due dates or deadline assigned.

As new feed entered to the same JIRA platform where every team member working, shows the progress of that project too. Nobody needs to search any other option to get the progress report of the project.

Defining issue types, fields, and workflows:

  • Issue types: issue types are entities that mirror real world objects. Software teams will often use issue types like bug, task, and user story.
  • Fields: fields track attributes surrounding each issue type. Bugs usually have fields like summary, description, fix version, and component to describe the area of software where the bug surfaces.
  • Workflow: workflow is the lifecycle of the object represented by the issue type. Bugs are found, reviewed, fixed, verified, and closed by several members of the team.


Recommended Issue types:

  • Bug
  • Task
  • User Story

Severity and Priority of Issues:

Recommended Severity:

  • Blocker/Show Stopper – Which blocks to test/use any other functionality.
  • Critical – Which has high impact on the business.
  • Major - Which has major impact on the business.
  • Minor - Which has less impact on the business.

Recommended Priority:

  • High – Need to be fixed immediately.
  • Medium – Should be fixed before release or in same build.
  • Low – Can be fixed in next release.


Recommended Workflow and List:

To Do – Any new ticket created by different team members should be stored under “To Do” list and Marked as “New”.

Development in Progress - Once dev team start working on any ticket it should be marked as “Open” and moved to “Development in Progress”.

Code Review – Once the development is completed it should be moved for “code review”.

Ready for QA on Stage – Once code review is completed it should be marked as “Fixed” and moved to “Ready for QA on Stage

QA Completed on Stage – If the result of testing is pass it should be marked as “Passed” and moved to “QA Completed”.

Note – Stage stands for Staging server.

Reopened – If the result of testing is fail it should be marked as “Failed” and work flow should be changed to “Reopened” and moved back to “To Do”.

Ready to deploy on Live – If the Testing result is Pass then Project Manager should move the ticket to “Ready to deploy on Live”.

Ready for QA on Live – This indicates that the ticket is ready for testing on live (Production server).

QA Completed on Live – This indicates that ticket is passed on live.

Reopened – This indicates that ticket is failed on live server and assigned back to responsible developer.

Done – Once the development and QA completed on live server project manager can mark that has done/closed.


---------- Document Completed ---------


Sometimes I am  amazed and observe that how a five minutes of relaxation just while having a cup of tea...Of course that too for namesake, in between the work of 8-10 hours of super focussed and super concentrated work schedule can bring an unbelievable change. A new change or better we call it "A new, good and joyous change".

It was Tuesday and 40 minutes to noon, I was having the second sip of my hot cup of tea and all of a sudden something very exciting flashed into my mind which was great and beneficial to do in all aspects. So, without uttering anything to anyone and I walked straight to Founder and CEO of my company and served all my ideas in front of him over his desk. After a generous discussion of 20 minutes, a notice came running downstairs and this was how our "TRIP TO KANAKPURA" was organized.