Greptile buying guide: Do two “Quantity” fields follow the same review rule?

Use two fictional modules to separate the issue context from rule scope before applying a checkout limit to a receiving report.

Source: www.greptile.com
November 16, 2026
2 min

Greptile describes two distinct sources of review context in its May 2025 announcement. An associated Jira issue can explain why a change was requested; a custom rule can be restricted to certain repositories, directories or matching files. The issue supplies the rationale; the scope says where the rule applies. A comment that links the right issue may still apply the rule in the wrong place.

“Quantity” can be an input or a total

A fictional props warehouse is revising a self-service checkout kiosk and a daily receiving report. Both mockups use “Quantity.” The kiosk asks how many items someone wants in one request; the report totals the items actually received that day. The issue concerns checkout limits, and the written rule applies only to the kiosk: at most 10 items per request. One hypothetical comment tells the team to cut the report’s total of 24 to 10 and cites that issue. Another points out that the kiosk mockup allows a request for 12 and names the kiosk as the rule’s scope. Only the second targets the part governed by the rule.

Give a reader the two mockups, an invented issue excerpt and a scope sheet. For each comment, ask which module it refers to, what the issue explains and whether the sheet supports applying the rule there. Mark “quantity exceeds the limit” as “scope unverified” if the comment does not identify the module. Reject a comment that flags the legitimate total of 24 even if it cites the right issue. This is a paper exercise, not code, a product test or a real issue.

When is Greptile worth considering?

Consider scoped review when modules share field names but follow different rules and issues live apart from review materials. Require comments to identify scope without flagging unrelated modules; don't judge by comment volume. If the boundaries are already obvious, adding a scope column to the manual checklist may take less maintenance. The team still decides which issue material can go to a third party and who maintains the scope. A comment is not approval to merge.

Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.

Original source:www.greptile.com