JIRA – for Issue Tracking

These are my experiences with JIRA for the Development Activity used for the issue tracking in our project.

About the Project, Team and Environment:

There were various teams like the web-app team, db team, ERP team, QA team, Integration team. There were issues from the various team and short releases almost daily release based on the criticality of the issue.

We need to handle Releases on different Environment (DEV,QA,UAT, Production)

For Developer : Each developer needs to know, what are assigned bug to them and start working on that.

For Manager: The manager needs to know, when the issue are getting resolved and going in which build the fix is done.

IT team: The IT head needs to track from the overall project tracking.

How JIRA is used:

Dashboard : JIRA provides a dashboard feature, each individual create their own dashboard about there issues and track them. This can be customizable by adding their own portlets into the dashboard.

Filters : we can create filters , to track the issues.

Subscribing : We can subscribe to the Filters. We will know, if there issues are shared between 2 different groups.

Watch: We can add watch list of the issues, some this is useful incase of clarification from different team and bug fix dependent on the other team.