Bugs and feature requests
Every bug report and feature request goes on the public tracker. There you can see what’s known and what’s been asked for, vote on what matters to you, and follow each one to the update that ships it.
Before you post
Section titled “Before you post”Search the tracker first. If your bug or idea is already there, vote for it with I have this bug too or I want this too. Votes decide what gets done first, and a comment with extra detail helps more than a second report.
Reporting a bug
Section titled “Reporting a bug”- Open the tracker and tap Sign in with Steam. You need to sign in with the Steam account that owns CRUMB. This is what keeps the tracker free of spam.
- Tap Report a bug. As you type a title, similar reports appear underneath. Check them first.
- Fill in the steps to reproduce, what you expected and what actually happened.
- Add your CRUMB version and system, and attach anything useful: a screenshot, your log file, or the circuit that shows the problem. Logs and circuits are only visible to you and the CRUMB team.
Suggesting a feature
Section titled “Suggesting a feature”- Sign in the same way, then tap Suggest a feature.
- Give your idea a short title. Similar ideas appear underneath: if yours is already there, vote for it instead.
- Say what you’d like CRUMB to do and what you’d use it for. What you’d use it for helps most, because it shows what the feature needs to do.
- If it helps, attach a sketch, a screenshot or a circuit that shows what you mean.
Following a report
Section titled “Following a report”Every bug and feature request shows where it stands. The two use the same steps, named for what they are:
| Bug | Feature request | Meaning |
|---|---|---|
| New | New | Posted and waiting to be looked at. |
| Needs info | Needs info | More detail is needed. Check the comments. |
| Researching | Researching | We’re looking into it before we say yes or no. |
| Confirmed | Planned | On the list. |
| In progress | In progress | Being worked on now. |
| Implemented | Implemented | Built, and coming in the next release. It changes to Fixed or Shipped when that release is out. |
| Fixed in x.y.z | Shipped in x.y.z | Done. The version is the update that contains it. |
| Duplicate | Duplicate | Already posted. Your vote has moved to the original. |
| User error | Already possible | Working as intended, or CRUMB can already do it. The comments say how. |
| Won’t fix | Not planned | Not something that will change. The comments say why. |
Fixed bugs and shipped features also appear on the roadmap under the update they arrived in.
Replies to your posts
Section titled “Replies to your posts”When you’re signed in, Your posts at the top of the tracker lists everything you’ve posted or commented on, newest activity first. A number beside it counts the posts with replies or a status change you haven’t seen yet, and each of those posts is marked in the list. Opening a post marks it read, and Mark all as read clears the lot.
Editing a post or a comment
Section titled “Editing a post or a comment”You can edit your own report or feature request, and your own comments, after you’ve posted them. Open the post and tap Edit your post, or Edit beside your comment. Everyone can see that it was edited, and when. Attachments can’t be changed after posting.

