Bugs and feature requests

Bug reports open at launch

Bug reports open on the tracker when CRUMB Advanced is released. Feature requests are open now, and ideas posted before launch might make it into 2.0.0. The steps for reporting a bug below apply from launch day.

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

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

1. 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.
2. Tap Report a bug. As you type a title, similar reports appear underneath. Check them first.
3. Fill in the steps to reproduce, what you expected and what actually happened.
4. 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

1. Sign in the same way, then tap Suggest a feature.
2. Give your idea a short title. Similar ideas appear underneath: if yours is already there, vote for it instead.
3. 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.
4. If it helps, attach a sketch, a screenshot or a circuit that shows what you mean.

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.
Confirmed	Planned	On the list.
In progress	In progress	Being worked on now.
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.