Team - On Track Concept Using JIRA and Confluence

If you are using JIRA and used its Search Feature to look for particular issue or list of issues, it's very cumbersome to do that every time.

One may find lots of Drop-downs for various fields for creating JIRA Filter Criteria using BASIC Query.

To do advance querying, one may require Knowledge about JQL – JIRA Query Language and fields used in JIRA.

Considering overall efforts to look-up and get stats every time one can store such queries as a JIRA Filter.

For a Scrum Master or Development Manager keeping track of various Features, Story-defects and Product issues is not an easy task for every day.

One have to think, Dev Manager generally takes care of multiple modules and different teams.

To do this task more productively, we can use Confluence along with JIRA to have customize Dashboard.

This article will help to know more about what your daily-dynamic Dashboard should have and how to prepare the one using Confluence-JIRA-Filters.

As I have pure technical background and love to follow coding principles, I am trying to avoid repeating the items each time and each place.

Before we dive into knowing what are the things to be done for Tracking the Team Stats, we should be knowing which items we should look for.

On day-to-day basis, every team generally works on Sprint tasks, so it may be Stories, Story Defects, Bugs, Testing or Miscellaneous Items.

All these things can be tracked in JIRA against different issue types by creating tasks and sub-tasks for EPIC, Story, Story Defect, Bug, Sub-Tasks, etc.

There is a good article about Agile-Sprint Planning, refer this link:requirements-epic-feature-user-story-task-size-and-estimation-in-agile-and-scrum.

Considering all the things are followed and are available in JIRA, now we have below items with us to track:

·         Product Backlog/Roadmap.

·         Bugs/Issues in released Product.

·         Current Sprint:

o   Stories, Defects, Sub-Tasks, Testing, Bugs etc.

·         Miscellaneous:

o   Quality Stats.

o   Performance stats.

I want to limit this article about Which things to be tracked in a Sprint using JIRA.

This who knows about JIRA Issue creation and its workflow usage, can move to next part of this article.

Please refer below diagram about creation of different issues and using JIRA attributes.

Every JIRA tasks has workflow associated with it. It is good to have information about respective workflow statuses.

Please refer below for EPIC/Story and can be customized based on your organizational strategy.