Ok, so if I’m understanding what you wrote, it seems like the current process is working (or close to working) for what your vision of function would be for a change of patrols.
The only issues occur:
- for scouts who have never been assigned to a patrol in Scoutbook, and
- for easier tracking of unit-specific tenure.
I can sorta see the first issue, although I would prioritize it way down the list as there is a work-around, albeit clunky, and it only applies once (i.e. for the first assignment to a patrol) for each scout.
The second issue is the one for which I’m still not seeing the use case. What difference does a quick-reference for the tenure in a particular unit matter? I could see value to quick-reference numbers for tenure in each program, i.e.
- tenure in Cub Scouts
- tenure in Scouts BSA
- tenure in Venturing
- tenure in Sea Scouts
- tenure in Exploring
insofar as we track that for service stars.
It’s not that I don’t see it as interesting data, just that I’m not sure why it’s interesting enough for the developers to code into the software.
ETA: I liked the idea of tracking tenure in different BSA programs so much that I submitted a new feature request. My guess is that it would be low on the priority list, if adopted by BSA development at all, but at least it’s out there to get on the list.
