How do I delete a merit badge that was incorrectly added? I read the recent forum posts on this topic and it seems the only way is to manually un-check each requirement one at a time. This prevents the merit badge from being shown as earned but how do I remove it completely? Is there an easier or quicker way? It was easy in Scoutbook Legacy but when I go there, it automatically directs me to Scoutbook IA.
There is no ability to remove a Merit Badge that was started by mistake. This does not harm the Scout as incomplete Merit Badges cannot be held against a Scout for any reason.
I can accept that, but could you make it easier for us? We have to manually uncheck the “approved” box for each requirement one at a time and then manually uncheck the date for each requirement one at a time. In Scoutbook Legacy, we could just delete it in a couple of easy steps.
@MattWeiss there is an existing story to make the process better - watch the change log for updates
It is unacceptable that you cannot delete a merit badge. We came back from summer camp and I have 1 Scout that did not attend, and several Scouts that dropped merit badges. You are saying that those merit badges will permanently show as pending or incomplete for the remainder of their time as Scouts when they have no intention of completing them.
No one is saying that, but it is more difficult than it should be. Some have said you can’t remove the “started” status.
The “started” status is exactly what I want to remove. We should be able to delete merit badges that the Scout is not going to work on. I understand that it has no bearing on a Scouts future progress but it would be good housekeeping to clean them out. Within the Troop, these badges would show up on incomplete merit badge reports that I use to track status. How can we request this feature that was previously available in Scoutbook to be made functional in Scoutbook Plus?
As Donovan noted, there’s an existing user story that’s been submitted to improve the MB process. Scouting America IT doesn’t publish timelines or details of planned features. So, as users we just have to wait for them to push the change for us to find out that it’s done (and what it does/doesn’t do). Thus Donovan’s advice to “watch the change log”.
That said, you could try escalating the issue to national via your council professional scouters. They have other avenues of advocating for changes (and potentially for prioritization of those changes) than the SUAC do. If you do that, the best chance of getting your preferred feature descriptions to national is to provide a clearly reasoned explanation of why the feature is important and why it needs to be prioritized, together with exactly what it should do. That way, the council professionals can forward that, rather than trying to translate from their notes of a conversation with you to whatever format they have to submit it to national in. Make sure you get the ticket number if they submit a MemberCare ticket, so that you can more easily follow-up with them on the issue (since you won’t get notice of what’s going on directly).
Thank you for clarifying the process. I appreciate all that you guys do with supporting us.
