The Issue Management component in Rommana not only supports all functionality that are supported by other bug tracking tools but also provides traceability of bug reports to test cases, use cases, and requirements. This traceability, which is enabled by the full integration of Rommana, makes issue management in Rommana superior to other bug tracking tools.
Some of the capabilities of Issue Management/Bug Tracking in Rommana include:
- The ability to create standalone issue reports that may not be linked to any test cases, scenarios, use cases, or requirements.
- The ability to optionally link an issue report to a requirement, a use case, a scenario, or attest case.
- The ability to manage issue reports throughout their lifecycle as they are handled by the development team and the test team.
- The ability to maintain the dependency between issue reports and test cases.
- Providing up-to-date detailed status of issue reports and progress on handling them.
- For Agile projects, the enhanced burndown chart for issue reports provides detailed information regarding creating and fixing (burning) issue reports over the course of a sprint or a release.
- Allowing developers to provide impact analysis information for each fix for the test team to use for effective regression testing.
- Allowing for tracking estimated and actual hours for working with issues.
- Providing a seamless integration of Jira as a bug tracking tool with Rommana to provide traceability of Jira bug reports back to test cases, scenarios, use cases and requirements in the Rommana repository.
- Maintaining the dependency between bug reports in Jira and test cases in Rommana.
- The ability to move issue reports between releases and sprints (iterations) to allow the scheduling bug fixes in different releases/sprints.