Jama's bug fixing process

By Kristina posted 01-28-2015 17:15

  

As much as we test and try to avoid them, bugs are inevitable in software. We appreciate your bug reports for two reasons: they alert us to a problem we might not know exists, and they help us gauge the impact and rank the severity. Receiving your bug report is crucial to the prioritization process.

Jama's bug process:

1. When you report unexpected behavior, one of us in support will attempt to reproduce the issue. If the issue is reported in the community but is not readily reproducible by us, we may create a ticket from the post so a more in-depth look can be taken.

2. We will recreate the issue on both the version you are using and the previous to determine if it is a regression. When we file a bug, we rate its severity based on how many users are affected and the effect (and if there is a workaround, how scalable it is.) We will link your ticket or community post to this bug, which is tracked internally with a bug ID.

3. We will provide the bug ID to you, which is used internally to track as it moves through development stages. We will also attempt to provide you a workaround at this point.

4. Members from three Jama teams meet daily to triage the bugs: Support, Engineering and Product determine if a bug will be targeted for a fix or not. While a time frame is not established in this meeting, the severity will be considered when our teams choose which bugs to target in a sprint.

5. Approximately once a month, a cross-functional team grooms our defect backlog. As a result, we decide some defects will be dropped from the backlog because they can no longer be reproduced; they are working as intended; or they have a very limited impact and severity. If the bug falls into one of these categories, we will contact you with an explanation.

An important part of our bug prioritization process is knowing how many customers are affected. For this reason, we do not proactively provide a full list of bugs or the steps to reproduce. Note that you can always cross-reference the provided bug ID with the release notes to see if a fix has been deployed.



0 comments
354 views