How issue statuses work
Every problem or idea you report becomes an issue. The issue board has one column for each status, from left to right. The column a card sits in tells you where the issue is right now and whose turn it is.
You find the board in your store admin under Settings → System → Issues, or by typing "issues" in the admin search. CartWhizz staff use Mastermind → Issues. To report a new problem from any admin page, use the bug button at the bottom right. Click How it works on the board for a short version of this page.
The normal path
Most issues go through these steps, left to right:
New → Triaged → Approved → In development → Ready for testing → Ready for production → Live – verify → Closed
- You report the issue. It starts in New.
- CartWhizz AI tidies it up and moves it to Triaged (usually within a minute).
- The CartWhizz team agrees to fix it: Approved.
- A developer starts work: In development.
- The fix is on the dev site (ecommerce.trooply.ai), not on live yet: Ready for testing. Now it is your turn.
- You test it on the dev site. It works, so you choose Passed on dev: Ready for production.
- The next release takes it to the live site, cartwhizz.com, and moves it by itself: Live – verify.
- You check it once more on cartwhizz.com. It works, so you close it: Closed.
Nothing goes to the live site until you pass it on dev. A release only ships the fixes in Ready for production.
Two side roads:
- Needs info: the team has a question for you. Answer it and the issue goes back to Triaged by itself.
- Reopened: the fix is still broken, on the dev site or on live. Choose Reopen and write what is still wrong. The team fixes it again, and it comes back to Ready for testing.
Each status
| Status | What it means | Who moves it here | What you do |
|---|---|---|---|
| New | Just reported. Nobody has looked at it yet. | You, by reporting it. | Nothing. Add screenshots or a video if you have more. |
| Triaged | CartWhizz AI (or the team) has read it and written a short summary. | CartWhizz AI or the CartWhizz team. Also happens by itself when you answer a question. | Nothing. Wait for the team to decide. |
| Needs info | The team has a question and can't go on without your answer. | The CartWhizz team. | Open the issue, read the question and reply in a comment. |
| Approved | The team agreed to fix it. It is waiting for a developer. | The CartWhizz team (in Mastermind). | Nothing. |
| In development | A developer is working on it. | The CartWhizz team. | Nothing. |
| Ready for testing | The fix is on the dev site (ecommerce.trooply.ai). It is not on live yet. | The CartWhizz team, once the fix is on the dev site. | Test it on the dev site. Works: choose Passed on dev. Broken: Reopen with a note. |
| Ready for production | You checked the fix on the dev site and it works. It waits for the next release. | You (the tester), or the CartWhizz team. | Nothing. The next release takes it live. |
| Live – verify | The release put the fix on the live site (cartwhizz.com). | The release, automatically. Nobody else can. | Check it on cartwhizz.com. Works: Close it as Fixed. Broken: Reopen with a note. |
| Reopened | The fix did not work. This is round 2 (or 3...). | You (the tester), or the CartWhizz team. | Nothing more. Your note tells the developer what is still wrong. |
| Closed | Done. Fixed, a duplicate, can't be reproduced, or won't be fixed. | You (the tester), or the CartWhizz team. | Nothing. If it breaks again, reopen it with a note. |
| Rejected | The team decided not to work on it. The reason is on the issue. | The CartWhizz team. | Read the reason. Comment if you disagree. |
Issues that were already in Ready for testing before this flow started (28 October 2026) keep their status. You can still close them as before.
Who is the tester?
Whoever reports an issue is its tester. You raised it, so you check the fix. Only you or the CartWhizz team can pass it on dev, close it or reopen it. Other people in your store can read it and comment.
Testing a fix
You test each fix twice: once on the dev site, once on live.
On the dev site (Ready for testing). You get an email. The fix is on ecommerce.trooply.ai, not on cartwhizz.com yet.
- Open the issue and read what was changed (the Pull requests box, the History and the comments show it). Each pull request says whether it is on dev and on live.
- Try the same steps that caused the problem, on the dev site.
- It works: choose Passed on dev. The issue moves to Ready for production.
- It is still broken: choose Reopen and write what is still wrong (for example "the button still does nothing on iPhone"). A note is required, so the developer knows what to look at. The issue becomes Reopened and the round number goes up by one.
On live (Live – verify). After the release, the issue moves to Live – verify by itself, with a comment naming the release.
- Do the same steps once more on cartwhizz.com. This is a quick check.
- It works: choose Close and pick Fixed. It is broken on live: choose Reopen with a note.
Reading the pull request chips
A pull request (PR) is the developer's change. The team links it to the issue, so you can see where the fix is.
- On the board, a card's PR chip names the pull request (for example "PR #1135"), or says how many there are. It turns green once every pull request is merged.
- On the issue page, the Pull requests box shows each one with where it is:
- Open: the developer is still working on it.
- Merged: the change is done but not on a site yet.
- Merged, on dev: it is on the dev site, ecommerce.trooply.ai. Test it there.
- On live: it is on cartwhizz.com.
- Closed, not merged: the change was dropped.
Where to test: on the dev site (ecommerce.trooply.ai) while the issue is in Ready for testing, and on cartwhizz.com once it is in Live – verify.
When "Needs info" is used
The team moves an issue to Needs info when they can't reproduce it or need a detail, such as which phone, which page, or a screenshot. They always write the question. Reply with a comment on the issue: the issue goes back to Triaged on its own.
Moving cards on the board
- Drag a card to another column. On a phone, press and hold the card first, then drag.
- Or use the Move to menu (the arrows button) at the bottom right of a card.
- Or open the issue and use the buttons under its description.
While you drag, the columns you can drop on get a blue outline. The others dim: that move is not yours to make (for example, only the CartWhizz team can approve), or it would skip a step. If you drop on a dimmed column, a message tells you which step comes first, such as "Move it to Approved first".
Some moves ask for a note before they happen: closing asks why, reopening asks what is still wrong, and asking for info asks the question.
Only a release (or the CartWhizz team) can move a card to Live – verify, so that column is dimmed for testers.
Tips for a good report
- One problem per issue.
- Say what you did, what you expected, and what happened instead.
- Add a screenshot, a screen recording, or a Loom, Google Drive or YouTube link.
- Search the board first (you can type
#42to jump to issue 42) in case someone already reported it.