Mind you, I have heard this from many senior QA professionals. When you ask a group of QAs, “What is JIRA?”- Many will answer that JIRA is a defect tracking tool. While this is one side of the coin, there is definitely another dimension to how people view the applicability of JIRA to QA or testing. Applicability of JIRA to Testing – An Alternative Dilemma Next time you have to work on it, don’t worry. So all in all, bug tracking/defect management in JIRA is very similar if not superior to dedicated bug trackers. If we have to review JIRA’s analytics in one word, it’s fantastic.Īdvanced/Power users of JIRA can also create advanced search filters to generate deeper insights.įor example, if want to look at all the defects assigned to you across multiple projects (BM and AB), you could use a JQL query like below: In addition, if you need reports go to “ Project – reports” and generate all sorts of reports as below: This supports better portability of your defect data, especially useful if you want to share your defect data with people who are non-JIRA users. #7) Defects can be exported into Word, XML, and printable formats Whichever way you use it, this is a big plus. Once they are reviewed and confirmed as valid, they can be imported all at once into the tool using this functionality. Also, if your team is new and you don’t want them creating issues directly into the tool, you can have them report the defects in an excel sheet. This aids the bulk creation of issues in JIRA at once. #6) Defects can be imported from a CSV file The relationship types are self-explanatory and the usage of simple-common-everyday-language words (such as relates to, caused by, etc.) makes it super easy and intuitive for any JIRA user to use this right. The resulting links will appear in the issue details page as below: Similarly, if a defect is blocking a requirement or is related to a requirement – you can make this aspect visible in JIRA. Let’s say if Defect 2 is a duplicate of Defect 1 you can establish that relationship. Link option in the JIRA issue fields lets you link a particular issue to another one. #5) Linking the defect to a requirement to enable traceability This allows for better visibility and collaboration with the development teams: #4) Comments and collaboration with the Dev TeamĮvery issue, its updates, people assignment, comments received from the Dev team – everything is tracked in JIRA under the activity log. For those, do not want to bother with the customization, you can’t go wrong with the default set up as well. This will need a little bit of customizing by your JIRA admin, but it is easy to do. #3) Defect Life Cycle:Īll bug life cycle statuses as in Bugzilla (or any other popular bug tracker) can be accomplished here too: In fact, more options such as labels, linking defects, estimating efforts can be used. Therefore, all the common facilities for defect reporting are available in JIRA too. Status of all issues is “To-Do” or “New” in JIRA by default on creating a bug. All issues will have a unique ID assigned to them by JIRA. These two fields are auto-created by JIRA. The two fields you are not seeing here are: Please note the fields highlighted in Red below: Status- All the statuses in the bug life cycleĪll the options are available to be able to create a defect effectively.Defect description (steps to reproduce).#2) Defect reporting needs the following information recorded for every issue: So, in JIRA to create a defect would be to create an issue of the type “ Bug”. #1) JIRA treats all work inside it as an Issue The Best Features of JIRA Bug Tracking Tool Additional Details About the Create Issue Page.Description of Fields on ‘Create issue’ Page.Creating a Jira Issue and Various Fields.Applicability of JIRA to Testing – An Alternative Dilemma.#7) Defects can be exported into Word, XML, and printable formats.#6) Defects can be imported from a CSV file.#5) Linking the defect to a requirement to enable traceability.#4) Comments and collaboration with the Dev Team.#2) Defect reporting needs the following information recorded for every issue:.#1) JIRA treats all work inside it as an Issue.The Best Features of JIRA Bug Tracking Tool.
0 kommentar(er)
