Skip to main content
All CollectionsFAQ
How ignored issues affect the status of code reviews
How ignored issues affect the status of code reviews

Incoherent code review results may occur immediately after ignoring issues; here is why and what happens under the hood.

Gabriele Gallo Stampino avatar
Written by Gabriele Gallo Stampino
Updated over a week ago

With Clayton, you can decide to ignore reported issues in some circumstances. For example, you might decide to accept the introduction of a piece of poorly performing code when it yields to a desirable benefit, such as improving the overall versatility of your solution.

Ignoring issues with a reason is a good practice to remove noise from your team and keep your code review reports relevant.

Review recalculation upon ignore

When ignoring an issue, Clayton automatically re-evaluates all the code review reports in which the issue appeared, to ensure that the results correctly reflect the decision to ignore and their status is reflected coherently in the integrated version control system.

The re-evaluation is a background process that can take some time to complete depending on various factors:

  • The complexity of the ruleset in use for your project.

  • The size of your project.

  • The number of review reports that need recalculation.

During this time you may temporarily experience some incoherent code review statuses. For example, a review can be temporarily marked as failed even if the issue that was causing the failure has been ignored.

Once the re-evaluation process completes, the results of all code review reports will be aligned, correctly reflecting their new status. This typically takes between 5 and 15 minutes.

Help needed?

If you need any further support, please drop us an email, we will be happy to help!

Did this answer your question?