I have found that when scoutbook is adding completion dates for merit badges it is putting the date I entered the requirements and not the date of completion. Where this is happening in situations where a requirement has something along the lines of “Do A or B” or “Do 4 of the following”. The sub requirements (ex. 2a, 2b, 2c…) will have their actual dates but the main requirement (ex. 2) that is checked off by scoutbook itself (you cannot check or uncheck this box yourself) is getting the date of the day I entered the requirements. This in turn ends up making the completion date for the entire badge the date the requirements were entered instead of the actual completion date. From our summer camp MB entry I have around a dozen badges with this issue.
Here is an example of the error. All the requirements for Rifle Shooting MB 2-Option A were marked complete by the summer camp on July 10. In scoutbook you cannot mark Option A or Requirement 2 complete. You have to enter all the Requirement 2 - Option A sub requirements and then scoutbook marks A and 2 complete itself. However it is putting the date of requirement entry into scoutbook as tghe completion date for the requirements instead of taking it from the subrequirements.
This bug was fixed a couple days ago.
You might need to undo one of the sub-requirements in order to see the change.
So its actually still putting the incorrect date in for the completion. I just went through and deleted a few requirements in one of the badges with this issue and now it puts yesterdays date as the completion date. And the badge completion date is still the date I originally put the requirements in and I cannot change it, it’s greyed out. I really hope I won’t need to totally remove all these merit badges and re-do them from scratch.
not seeing this behavior - but I did use a clean scout - looking for one with this issue
I can say for sure that this bug has not been fixed. I went to one of the scouts that had this issue with Rifle Shooting merit badge. I totally removed the badge from the scout and then re-entered all the requirements. And once again it did not pull the dates from the sub-requirements. However it also did not pull the current date, like it did last night when I posted, it took yesterdays date. So it seems that all they did when they “fixed” the bug was make it take the day before the data was entered instead of the day it was entered.
The scout in question is BSA member ID: 131714869, scoutbook user ID: 239561.
yeah we saw that and reported it today after you mentioned it - is not a nice bug - but thanks
We just noticed this tonight, so it’s still occurring.
Has this bug been fixed?
Fixes will be reported in the change log. They may or may not be mentioned in a thread that reported it (don’t count on it, but sometimes they are). The timing and priority of fixes are not communicated (yes, it would be nice, but no, they don’t say). With that said, bugs do seem to have priority over improvements/changes (which makes sense).
This bug has not been fixed.
@WilliamAbbott1 The bug was fixed earlier this week.
If you are still having issues, we would need more details.
Hello Jennifer!
As of today, it’s still a problem. It’s the basic set a sub-Requirement and the Requirement is set to the date you made the change, not the MB date. This flows up to the MB completion date.
@WilliamAbbott1 I just tested it, and it worked for me. So, we need more details about what you are seeing in order to reproduce it.
Yes was it entered today or like 2 weeks ago @WilliamAbbott1 ?
Hello Jennifer!
It seems to report the dates correctly now after I go in and reapprove the sub-task and set the overall completion date as well. Thank you for your help!
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
