Like other software companies, we use an issue tracker. There are lots of trackers out there
and our company works with JIRA, one of the most common tools in use today. JIRA
is modern and intuitive, and even offers an annual practical joke.
Due to recent requests by people from within and without my
company to explain how I use JIRA in the testing environment and for the
tracking of version status, I will offer a few tips and links that may help you
start using JIRA like I do.
Filters and (JQL)
Filters are the basis for a lot of
the analysis work you can do in JIRA. They are saved queries that can be run in
basic mode (form based) or advanced mode (JQL).
JIRA has its own query language - JQL, don’t be afraid to use it. Its intuitive nature will be much appreciated,
especially if you are familiar with different kinds of queries.
In addition, when you become familiar
with the JQL mode, you’ll find it much easier and faster to use than the basic
mode.
Options for filters include managing
them, sharing them with others, keeping them private, cloning them (which can save
lots of time), and more.
Regression
A useful checkbox field can be added to
each bug to indicate if it is a regression. The quality policy in my company is
not to approve a release if a regression exists and every regression must be
corrected immediately.
Dashboards and Gadgets
In JIRA, you can create as many
dashboards as you want and configure them to suit your requirements. You can
also share your dashboards with others or keep them private.
o
“Recently Created Chart”
In my company, we use this chart
together with the filter of all bugs found in the tracked version that have a priority
higher than major or are marked with “regression”. I expect that as we move closer
to the release date, the amount of active bugs will decrease and the columns
will appear in green (meaning the bugs were fixed).
o
Tracking a risk area in
your project
You can use the pie graph in JIRA to
locate problems in the project. For example, you can create a pie graph with
statistical information indicating regression. This will help you discover if
your project has a problem with its work processes.
As another example, you can use a
statistical graph for different system components to determine where most of
the bugs in the system occur and why.
Hierarchical trees
Truth be told, this is one of the most
important features that JIRA lacks. However, you can work around this by using epics
and user stories. In addition, make sure bugs are linked to epics.
Although this may not provide a
perfect solution, it does a good job of covering the issue and helps gather all
the bugs in one place.
Another option is to use a Structure plugin.
Hierarchical trees
Truth be told, this is one of the most important features that JIRA lacks. However, you can work around this by using epics and user stories. In addition, make sure bugs are linked to epics.
Although this may not provide a perfect solution, it does a good job of covering the issue and helps gather all the bugs in one place.
Another option is to use a Structure plugin.
Plugins
Here are a few plugins you may want
to check out:
o Capture (older name: Bonfire) - Great for exploratory testing
and the latest word in software testing. If you use this tool, make sure to
read about the special annotation in the notes .
o Zephyr for JIRA - If you can live without hierarchical trees,
you may find this tool useful when it comes to managing your manual tests.
