PRODUCT / ISSUES

Bug reports your coding agent can act on.

Cofactor files bugs in Jira, Linear or Azure DevOps with repro steps, evidence and a prompt your agent can use to fix them.

issues.northwind.io/ENG-2214
NNorthwind
▤Inbox3
◈My issues
◇Triage2
▶Active
☰Backlog
▣Projects
Engineering›Triage›ENG-2214
ENG-2214TodoBug

Expired promo code leaves the order total unchanged

What happened

Applying an expired promo code at checkout shows the success banner and leaves the order total unchanged, so the cart and the total disagree. The customer can place the order at the undiscounted price while the page says the code was applied.

Steps to reproduce
  1. Sign in as a returning customer with a saved card.
  2. Add any item to the cart and open checkout.
  3. Apply promo code SPRING24, expired 2026-06-30.
  4. Read the banner, then read the order total.
EvidenceRun video · 0:42TraceNetwork log
Prompt for your coding agentCopy
Fix ENG-2214 in the storefront checkout.

When a promo code has expired, applyPromo() returns { ok: false, reason: 'expired' },
but PromoBanner still renders the success state and OrderSummary does not recalculate
the total. The cart and the total disagree.

Reproduce from the recorded trace: cofactor test-suite steps checkout-promo 8f21c4
Make the banner reflect the rejection and keep the total authoritative.

Cofactor re-runs the Checkout suite on your PR and comments the result.
StatusTodo
PriorityHigh
Assignee
Priya Raman
Labels
regressioncheckoutbilling
ProjectCheckout hardening
Filed by
Cofactor
from CF-3391 · 8h ago
Todo

Expired promo code leaves the order total unchanged

ENG-2214 Checkout hardening
PriorityHigh
AssigneePriya Raman
Run video · 0:42TraceNetwork log

What lands in the ticket.

Most automated bug reports are a stack trace and a screenshot, and someone still has to work out what happened. Cofactor’s reports include everything needed to understand and fix the bug.

Repro steps

The exact steps and the data used, written so a person can follow them by hand.

Evidence

The ticket links to the run video, the trace and the network log.

An agent prompt

A ready-made prompt that names the failing call and the command to replay it. Paste it into your coding agent.

Deduplication

If the same failure happens in ten runs, you get one ticket with a count.

Filed in the tracker you already use.

01

Jira

Set up the project, issue type and fields once. Cofactor files issues under its own name, so the audit trail stays clear.

02

Linear

The team, label and priority come from the suite that found the bug, and the issue links to the run.

03

Azure DevOps

Work items are created in the right area path, ready for your next sprint planning.

Common questions.

Does it file duplicates?

No. If a failure happens again, Cofactor adds it to the existing issue instead of opening a new one.

What if the failure is our test, not our product?

Then it isn’t filed as a bug. Cofactor replays every failure before reporting it, and a broken test is handled as maintenance instead.

Can we review before anything is filed?

Yes. You can turn on a setting that holds findings for a person to review, and only what you approve reaches your tracker.

Let your coding agent fix the bugs Cofactor finds.

Join the waitlist, or book a call to see a filed ticket end to end.

Book a call