Skip to main content

Issues review

At least once a week, we should review the issues on our repo and make sure that they follow our Issue Template, check the Acceptance Criteria and Use Cases, and make sure that there's enough information for creating the test plan. The goal is to have at least every issue in the Current Sprint column with all this information; this will also help the developer understand the primary purpose of the issue created and how that will generate value for our project.

Priority of reviewing issues by status column#

There's a priority order that we need to follow to have everything organized and in a way that makes sense for our project. The order of priority by column are the following:

  1. In review/QA
  2. In Progress
  3. Current Sprint
  4. Next Sprint
  5. Backlog

Issues that are already on the Ready to merge column doesn't need to be updated since almost all the work has been done on the issue. Let's talk about why this prioritization on each column:

In review/QA#

That's most important to have the right scenarios since it will help us create the test plan, understand the feature, and automate.

In Progress#

That's important to have all the scenarios at this stage since we can start creating the test plan earlier for the issue.

Current Sprint#

By having the scenarios created at this stage, the QA can already start acting on creating a test plan and identifying if there are things that can lead to errors earlier.

Next sprint#

Ideally, the QA team should create all the scenarios while the sprint is at this stage; that means that we'll not have to worry about it when it's moved to the Current Sprint, and we have enough information to estimate the effort for the issue.

Backlog#

If the issue is essential and we know that someone will tackle it soon, we can start creating all the scenarios for the case earlier as in Backlog, but usually, we want to create it on the Next Sprint column.