| Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
release_18.3 [2023/08/28 17:58] admin [Bug Fixes] |
release_18.3 [2023/08/28 18:05] (current) admin [Deprecating Areas] |
| ===== Patch (2023-08-28) ===== | ===== Patch (2023-08-28) ===== |
| ==== Import from MyScouts ==== | ==== Import from MyScouts ==== |
| BUG: IMPORT: SS-5437: Group-wide imports of unpopulated sections could time out | A variety of bug fixes and tweaks relating to importing rosters, most notably the ability to import CSV files. |
| ENH: IMPORT: Suspend syncing while doing import from MyScouts, so the progress bar doesn't get dismissed | |
| ENH: IMPORT: Better text when an import fails (e.g., due to a timeout) | * IMPORT: SS-5437: Group-wide imports of unpopulated sections could time out |
| ENH: IMPORT: Now support CSV format (RFC4180) | * IMPORT: Suspend syncing while doing import from MyScouts, so the progress bar doesn't get dismissed |
| | * IMPORT: Better text when an import fails (e.g., due to a timeout) |
| | * IMPORT: Now support CSV format (RFC4180) |
| |
| ==== Deprecating Areas ==== | ==== Deprecating Areas ==== |
| ENH: COMMITTEE: Restrict third-party create to official Group-level accounts | |
| ENH: COMMITTEE: Wire off creating more Council accounts. Can be left as a support exercise if someone really needs a non-official Council account. | Areas were eliminated from the Scouts Canada organizational hierarchy a few years ago, but persisted in ScoutsTracker. The absence of Areas means that some UI changes had to be implemented to prevent creation of Area-level accounts, and to make it easier to find/select the desired Group from the now-large number of Groups within a Council. |
| ENH: COMMITTEE: Clean up references to "Area" where Area accounts can't be created | |
| ENH: Added "search for" box above the list of Groups (which can get quite large) | * COMMITTEE: Restrict third-party create to official Group-level accounts |
| ADMIN: Implement an "collapseArea" method | * COMMITTEE: Wire off creating more Council accounts. Can be left as a support exercise if someone really needs a non-official Council account. |
| | * COMMITTEE: Clean up references to "Area" where Area accounts can't be created |
| | * Added "search for" box above the list of Groups (which can get quite large) |
| | * Sort Groups by Group name, then number. E.g., "1st Muddy Paw, 9th Muddy Paw, 2nd Rubber Boot, 9th Rubber Boot". |
| | * ADMIN: Implement an "collapseArea" method |
| |
| ==== Miscellaneous Enhancements ==== | ==== Miscellaneous Enhancements ==== |
| ENH: Removed legacy migration code | * Removed legacy migration code |
| ENH: Moved a bunch of the start up tips to auto-generated news feed posts | * Moved a bunch of the start up tips to auto-generated news feed posts |
| ENH: COMMITTEE: Tweaked welcome message wording for Committee Members | * COMMITTEE: Tweaked welcome message wording for Committee Members |
| BUG: SS-5458: COMMITTEE: Group committee accounts weren't seeing Council events | * SS-5458: COMMITTEE: Group committee accounts weren't seeing Council events |
| ADMIN: Implement an "add/replace GC" method | * Implement an "add/replace GC" method |
| |
| ==== Bug Fixes ==== | ==== Bug Fixes ==== |
| BUG: SS-5419: Paddling Skills 3 number of expeditions wasn't being automatically added as related requirement for events with Paddle Expedition label | * SS-5419: Paddling Skills 3 number of expeditions wasn't being automatically added as related requirement for events with Paddle Expedition label |
| BUG: SS-5428: Parents couldn't click on Parent/Guardian Consent link in list view for events who's deadline had already passed | * SS-5428: Parents couldn't click on Parent/Guardian Consent link in list view for events who's deadline had already passed |
| BUG: Scouter role tags weren't showing on most lists | * Scouter role tags weren't showing on most lists |
| BUG: SS-5456: Some instances of login where account-wide reply-to address wasn't overriding login-specific reply-to address | * SS-5456: Some instances of login where account-wide reply-to address wasn't overriding login-specific reply-to address |
| | |
| |