Tickets Management Module
Why you need the Ticket Management Module ?
Control the complete workflow for various Ticket Types including risks, issues, tasks and enhancements management
Generate comprehensive metrics for identified root causes and severity levels
Support various defect supportive information via attachments
Design and establish workflows for improved re-test visibility via automatic notifications
Graphical reports based on severity, priority, defect type, defect category, expected fix date and much more
The QACoverage Ticket module is but one part of a fully integrated test management solution that includes requirements tracking, test case management, reporting, and agile integration. This module allows users to create defects during or outside of test runs, import defects in bulk, track their progress, and manage defects within agile sprints.
Manage most commonly used ticket type
In nearly every ticket management tool, users can create and edit defects. But with QACoverage, ticket tracking and management is much more detailed. While most commonly used ticket type is Defect, QACoverage also offers options for Risk, Enhancement, Question, and Task – each of which have their own detail fields available.
Assignee field can help track the workload
During or after creation, tickets can be pulled into Sprints, assigned to any QACoverage user, attached to test cases (and by association, test runs), and tracked using the various available statuses. The assignee can be changed as needed as the ticket moves from developer to tester and back again. Or if developers don’t use QACoverage, the assignee field can help track the workload for each tester.
Defect management and tracking simple and easy
The Ticket Management section gives a detailed overview at-a-glance using either a grid with filtered columns or a color-coded pie-chart. The grid offers the defect summary, product version, assignee, sprint, defect type, and status with filtering options on each column. While in the ticket tracking section, users can create new tickets, import them in bulk, export, edit existing ones, archive, or add defects to sprints. All of these options make defect management and tracking simple and easy.
Key Features and Benefits
- Gives the ability to create different main defect types with details specific to each type
- For the main bug type, an amazing level of detail can be gathered
- Quick pie-chart view of bug statuses
- Ability to monitor defect tracking progress with ease
- Ability to pull defects into sprints
- Enables easy connection of defects to test cases during execution
Plentiful Ticket Details Aid in Defect Remediation
When the ticket type, Defect, is chosen – generally the most commonly used defect type in software development – users can choose to enter enough information to make root cause analysis considerably easier. In addition, regression tests can be more focused in historically troublesome areas, such as certain operating systems, browsers, or devices. All of the available information also makes progress tracking extremely simple.
This quick summary is shown in the defect tracking grid, so it’s best to keep it brief.
The person creating the defect is automatically recorded, but the assignee could be the developer and then later the QA professional retesting it.
Options area Minor, Major, Critical, and Blocker.
Choose from any of the major browsers to help the developers isolate the defect cause.
Options are Low, Med, High, and Urgent.
Entering this information helps to show which versions were defect heavy, thus pointing to areas of the application that may need regression testing focus.
This helps narrow down the defect to aid in developer assignment, tester assignment, and automation updates. Options are UI, Functional, Database, Localization, Compatibility, and Performance.
Applies primarily to desktop applications.
A full length description can be added and formatted here with the WYSIWYG.
Defect statuses available are: Open, New, Assigned, In Progress, Ready for Promotion, Ready for Retest, Re-open, Rejected, Suspend, and Requires More Info.
Current or future sprints can be selected for planning purposes.
Options are Desktop, Tablet, and Mobile.
This text field can narrow down the defect cause even further.
To aid in fixing the defect, documentation can be added.