User Tools

Site Tools


release_2.0

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

release_2.0 [2017/07/29 15:17]
admin created
release_2.0 [2020/12/23 17:11] (current)
Line 1: Line 1:
 +[[Release Notes|<< List of all previous releases]]
 +====== Release 2.0 - Key Features ======
 +===== Outings and Events =====
 +  * Can record outings and events, and associate youth with those events
 +  * Events can be labeled (e.g., 'camp', 'hike', 'community service') for easy determination of badge requirements (e.g., V. Outdoor skills requires 6 nights of camping and 2 six-hour hikes, V. Citizenship requires 5 hours of communty service)
 +  * Youth/parents have their own view of events, filtered to just those that they've participated in
 +  * Events are fully-searchable
 +  * Events and related badges/awards are cross-linked... badges impacted by various labels are automatically cross-linked.
 +  * Similarly, each badge and award shows the events that may contribute to requirement completion
 +  * Youth can be selected for badge completion based on event participation
  
 +===== Miscellaneous Enhancements =====
 +  * Parent Logins can change their own password
 +  * By-Badge report grouped by patrols
 +  * By-Badge report now has sub-selection by individual requirement
 +  * Consistent presentation of patrols (sorted by name)
 +  * Allow badge completion logic to be overridden in DB
 +  * Allow badge requirement re-ordering/re-labeling
 +  * Easier selection of multiple youth
 +  * Filter youth by need (who doesn't have the badge) when multi-selecting youth
 +===== Bug Fixes =====
 +  * Synced updates for awarded badges weren't applying the timestamp
 +  * Apply awarded badges timestamp for non-db impletantions (e.g., FireFox)
 +  * Corrected escaping/encoding of data (now supports display names like "Alice & Bob")
 +  * TROOP: P.Personal Development #5 was missing from the database!
 +  * Completion changes made to multiple youth, after viewing reports are now correctly reflected in Reports
 +  * Finally nailed the source of the "white screen"