Changes for page Changelog
Last modified by Treyfane Dingo on 2025/07/12 14:20
From version 141.2
edited by Treyfane Dingo
on 2025/07/12 14:19
on 2025/07/12 14:19
Change comment:
There is no comment for this version
To version 55.1
edited by Treyfane Dingo
on 2023/11/29 02:32
on 2023/11/29 02:32
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -3,249 +3,9 @@ 3 3 All user relevant changes to L.A.S.S.I.E. will also be explained in our L.A.S.S.I.E. Developer News Channel [[https:~~/~~/t.me/+DouU4F1US69mYzhk>>https://t.me/+DouU4F1US69mYzhk]] 4 4 ))) 5 5 6 -=== 1.8.48 (12.07.2025) === 7 - 8 -* Changed messages in Operations Status about adding / removing / informing units to and from Incidents to give a clearer picture if more than on 9 -* Bugfix: Changed maximum field length for floor in Incident Management to 6 and changed form field to reflect maximum length 10 - 11 -=== 1.8.47 (05.07.2025) === 12 - 13 -* Bugfix: added timezone consideration to the Briefings, Items DB and Assets DB modules and the Bigscreen 14 -* Bugfix: Changed maximum field length for floor in Incident Management to 6 and changed form field to reflect maximum length 15 - 16 -=== 1.8.46 (18.06.2025) === 17 - 18 -* Changed Show Incident to include a better functionality to search for attendees in Involved and Witnesses 19 - 20 -=== 1.8.45 (14.06.2025) === 21 - 22 -* Bugfix: the .ics will now also work in Thunderbird (which is way more strict than everything else if it comes to slight formatting errors in an .ics …) 23 - 24 -=== 1.8.44 (06.06.2025) === 25 - 26 -* Bugfix: Various smaller spelling corrections 27 -* Changed standard Attendee CSV importer to make it more robust 28 -* Added standard Event (Schedule) CSV importer 29 -* Changed Autofill ODS-C script to accommodate for multiple parallel ODS 30 - 31 -=== 1.8.43 (14.04.2025) === 32 - 33 -* Bugfix: Correctly displaying error messages for missing Lat/Long in Location Management 34 -* Bugfix: Correctly displaying missing Nationality in Operatives Lists 35 - 36 -=== 1.8.42 (09.04.2025) === 37 - 38 -* Bugfix: Setting an Operative to INACTIVE now also sets the Access Level “No Access” 39 - 40 -=== 1.8.41 (02.04.2025) === 41 - 42 -* Added standard CSV importer to Attendee Database for all clients without individual JSON API importer 43 - 44 -=== 1.8.40 (30.03.2025) === 45 - 46 -* Bugfix: Fixed Permissions for Location Database entries 47 -* Updated Schedule and Self-Scheduler, secured and updated POSTVAR / SQL statements 48 -* Changed Operations Status and enabled COMBIUNITS with no scheduled Operatives 49 - 50 -=== 1.8.39 (20.03.2025) === 51 - 52 -* Bugfix: Alerting of Dispatch for Status 9 and 5 works correctly again 53 - 54 -=== 1.8.38 (02.03.2025) === 55 - 56 -* Added a Radio Log function for DMR calls, which can be used with a FurCom Radio Logger 57 -* Bugfix: Fixing many bugs in CSS, surely building in more 58 - 59 -=== 1.8.37 (25.02.2025) === 60 - 61 -* Added a whole new location mapping system to Incident Management which makes use of OpenStreetMap and can make use of a C3Nav compatible navigation system, e.g. EFnav 62 -* Added a function to L.A.S.S.I.E. Bot to enable Operatives to send their current geo-location which then can be used by Dispatch to find them on OpenStreetMap 63 - 64 -=== 1.8.36 (24.02.2025) === 65 - 66 -* Bugfix: debugged about a thousand bugs from Operations Status 67 -* Changed the whole pager system connector in Operations Status to better show the status of connections, auto-reconnect on connection failure, and have a pager status symbol just below the L.A.S.S.I.E. menu 68 -* Changed the context menus in Operations Status to not show pager sending options when the pager system is down or unavailable 69 - 70 -=== 1.8.35 (21.02.2025) === 71 - 72 -* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC 73 - 74 -=== 1.8.34 (20.02.2025) === 75 - 76 -* Changed the complete JavaScript in Operations Status so the page is about 500% faster 77 -* Changed the stale counter for Incidents which now takes recent log entries into account, so a long-sunning incident with a recent log entry isn't shown as red blinking stale for half the day any more 78 - 79 -=== 1.8.33 (11.02.2025) === 80 - 81 -* Bugfix: Removed some bugs from Qualification Management and Event Management that occured while adding stuff in Operatives Management 82 - 83 -=== 1.8.32 (31.01.2025) === 84 - 85 -* Added external alerts to Incident Archive list 86 -* Bugfix: Lost & Found and Item Database now also accepts photos via L.A.S.S.I.E. Bot if they are of rather low resolution. 87 -* Bugfix: Files are now also accepted if the extension of an allowed file type is in UPPER CASE. 88 - 89 -=== 1.8.31 (06.01.2025) === 90 - 91 -* Changed Briefing module to not have access levels any more, since they necessarily have been "W" for everybody anyways 92 -* Bugfix: Operative Collar IDs of C-Units in Operations Status now are correctly shown if > 999 93 -* Bugfix: Incident Archive table now does not reset scrolling position every 15 seconds any more 94 -* Bugfix: Operatives Duty Stats table (and others) now also scrolls header horizontally, not just content 95 -* Changed location of several files and scripts (backend) 96 - 97 -=== 1.8.30 (27.12.2024) === 98 - 99 -* Added direct Telegram link to most of the Telegram Handles in Operatives Management and Operatives Lists 100 -* Added an upload function for training certificates to Qualification & Training in Operatives Management; the qualification types First Aider, EMT / Paramedic, 34a, SiA, Firefighter and M.D. will require a certificate to be uploaded upon adding or changing them 101 -* ((( 102 -Changed the add and change form for the qualification types First Aider, EMT / Paramedic and Firefighter in Qualification & Training in Operatives Management to account for standard training levels 103 -))) 104 - 105 -=== 1.8.29 (21.12.2024) === 106 - 107 -* Added autocomplete for the Item Type in Lost & Found Database – it will display the types from all lost or found items, but not the returned ones 108 -* Updated search field in Lost & Found Database to also search inside the Log Comments 109 -* Updated table scrolling behaviour to be more mobile friendly and coherent 110 - 111 -=== 1.8.28 (17.12.2024) === 112 - 113 -* Added an option to change all duties / events with the same title in the Schedule at the same time 114 - 115 -=== 1.8.27 (16.12.2024) === 116 - 117 -* Added options to only show one particular status to Lost & Found Database which should make it more easy to display items reported as lost only 118 -* Added a delete option for Lost & Found images (click item to edit, then trash can next to image upload) 119 -* Added Log comment field to Add Lost & Found item 120 - 121 -=== 1.8.26 (16.11.2024) === 122 - 123 -* Updated ConOps Incident Management, secured and updated POSTVAR / SQL statements, added error codes and error log 124 -* Added most of the recent features from Incident Management to ConOps Incident Management 125 - 126 -=== 1.8.25 (20.10.2024) === 127 - 128 -* Added a module for changing Item Clearance Levels to System Settings 129 -* Changed the Log Reports printable from Incidents to a more readable format 130 -* Added an Incident Report to print out the whole Incident 131 - 132 -=== 1.8.24 (05.09.2024) === 133 - 134 -* Added a System Setting to prevent Operatives un-registering from a duty in an otherwise writeable Self-Scheduler 135 - 136 -=== 1.8.23 (30.08.2024) === 137 - 138 -* Added a FAQ system for L.A.S.S.I.E. Bot to answer questions in a non-PM Telegram chat with the word "tell" as trigger if directly addressed (e.g.: "@LassieBot tell me about Tuesday"). Answer keywords and answers can be set in System Settings → Bot FAQ Answers. The Telegram chat IDs, which the bot shall answer questions for any convention in, have to be set as comma separated list in System Settings → Settings → Group IDs of L.A.S.S.I.E. Bot FAQ System. 139 - 140 -=== 1.8.22 (29.08.2024) === 141 - 142 -* Updated Self-Scheduler to include duty stats for the respective Operative 143 - 144 -=== 1.8.21 (27.08.2024) === 145 - 146 -* Updated Schedule to also send information about //what// has changed to scheduled Operatives on change of the content of a schedule item via L.A.S.S.I.E. Bot 147 - 148 -=== 1.8.20 (21.08.2024) === 149 - 150 -* Added a direct link to the Schedule of respective Operatives (click on the collar ID) to the Scheduler event popup 151 - 152 -=== 1.8.19 (11.08.2024) === 153 - 154 -* Updated Operatives Duty Stats to make the table more readable. Also added EVAC as shift type. 155 - 156 -=== 1.8.18 (10.08.2024) === 157 - 158 -* Updated the Self-Scheduler so that the buttons are better readable; also got rid of the "Save" button 159 - 160 -=== 1.8.17 (17.06.2024) === 161 - 162 -* Bugfix: All language characters can now be used for searches in Schedule and Self-Scheduler 163 -* Bugfix: Special unicode language characters like the ꝥ which is a þat (þ) wið a stroke, and dating back to Old Engliſh, can now also be used in Schedule titles. One can alſo uſe emojis 😸 now ... why are you torturing me so much? 164 -* Added a searchable field for Car License Plate to Attendee DB. This can be imported from a REG DB via API or CSV. 165 - 166 -=== 1.8.16 (14.05.2024) === 167 - 168 -* Bugfix: DOB can now again be initially set by users with write access to the Operatives Database 169 -* Bugfix: Convention Rank can now be set again by users with write access to the Operatives Database 170 - 171 -=== 1.8.15 (29.04.2024) === 172 - 173 -* Updated Operatives Management so users with write access to the Operatives Database can no longer change Operative PII for Operatives once it is initially set; Operative PII has to be changed by the Operative themselves 174 -* Removed height / weight from Operative Database (unneeded PII) 175 -* Added the ability to change the Nickname for the Operatives in Personal Preferences 176 - 177 -=== 1.8.14 (19.04.2024) === 178 - 179 -* Updated Operatives Management so users with write access to the Operatives Database can no longer set access permissions that exceed their own 180 -* Removed the Messaging Module as it was not used any more 181 -* Updated Operatives Management, secured and updated POSTVAR / SQL statements, added error codes and error log 182 -* Updated PNG Management, secured and updated POSTVAR / SQL statements, added error codes and error log 183 - 184 -=== 1.8.13 (16.04.2024) === 185 - 186 -* Updated ARO Management, secured and updated POSTVAR / SQL statements, added error codes and error log 187 -* Updated Item Type Management, secured and updated POSTVAR / SQL statements, added error codes and error log 188 -* Bugfix: Items in the Item DB can now be edited if the item type that has been originally used was since deleted 189 - 190 -=== 1.8.12 (18.03.2024) === 191 - 192 -* Updated Schedule to be able to send an information to scheduled Operatives on change of the content of a schedule item on request via L.A.S.S.I.E. Bot and to auto-send an information via L.A.S.S.I.E. Bot in case a schedule item is moved or deleted 193 - 194 -=== 1.8.11 (17.03.2024) === 195 - 196 -* Updated L.A.S.S.I.E. Bot to include a reset password function 197 -* Bugfix: Hitting [Enter] now properly closes the dialogue window when creating new API Keys in API Keys Management 198 - 199 -=== 1.8.10 (14.03.2024) === 200 - 201 -* Bugfix: Changing more than one access level in Operatives Management to a non-standard access level did not work correctly; it now does and even so without having to F2/save and reload the page 202 - 203 -=== 1.8.9 (10.03.2024) === 204 - 205 -* Updated Operations Status to better reflect non-ongoing incidents since the fire mini-icon was not visible enough; non-ongoing incidents will now be displayed without a frame around the incident information instead 206 - 207 -=== 1.8.8 (08.03.2024) === 208 - 209 -* Bugfix: ARO was not correctly displayed in Show Incident if incident was not ongoing 210 -* Bugfix: Incident Opening Time was incorrectly (re-)set on incident update under certain circumstances 211 -* Bugfix: Some read-only input fields were not correctly displayed as read-only 212 - 213 -=== 1.8.7 (01.03.2024) === 214 - 215 -* Bugfix: tables in Lost & Found Database, Personal Assets Database and Items Database now refreshes on the currently selected page rather than to the first page 216 -* Bugfix: change of Personal Asset now does not mess up the dialogue window any more 217 - 218 -=== 1.8.6 (25.02.2024) === 219 - 220 -* Updated Show Incident to make Log Comments individually printable 221 -* Updated Show Incident to make Log Comments deletable by the owner or Admin; deleted Log Comments will still be shown to the original owner of the Log Comment and Admins but not to other operatives 222 -* Updated Show Incident to make Log Comments flaggable as //Medic Log (Confidential)// by the owner or Admin after saving 223 - 224 -=== 1.8.5 (04.02.2024) === 225 - 226 -* Updated Operative Collar ID / nickname in top right corner to directly link to Personal Preferences on click 227 - 228 -=== 1.8.4 (15.01.2024) === 229 - 230 -* Updated Show Incident to display Medical / File log comments in another colour 231 -* Updated Show Incident to add a standard Patient Report text to Log Comment if //Medic Log (Confidential)// is selected upon an empty Log Comment field 232 - 233 -=== 1.8.3 (26.12.2023) === 234 - 235 -* Updated Lists in Operatives Management to differentiate between the UnitTypes in regards to inactive Operatives 236 -* Added button in Operatives Management / Lists to copy respective Wiki List on click 237 -* Added information about duration of inactivity to inactive Operatives in Operatives Management Lists 238 - 239 -=== 1.8.2 (01.12.2023) === 240 - 241 -* Updated Briefings to not show briefings sent by the Operative themselves per default and added a checkbox to also show those briefings 242 -* Updated Briefings to show sent briefings in green and unread briefings in orange 243 - 244 244 === 1.8.1 (29.11.2023) === 245 245 246 246 * Updated Schedule to show the currently running half hour as slight grey overlay 247 -* Updated Briefing Management, secured and updated POSTVAR / SQL statements, added error codes and error log 248 -* Updated Briefing Management forms and mobile layout to be more mobile friendly 249 249 250 250 === 1.8.0 (25.11.2023) === 251 251