Changes for page Changelog
Last modified by Treyfane Dingo on 2025/08/19 22:33
From version 147.1
edited by Treyfane Dingo
on 2025/08/19 21:38
on 2025/08/19 21:38
Change comment:
There is no comment for this version
To version 134.2
edited by Treyfane Dingo
on 2025/04/09 16:01
on 2025/04/09 16:01
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -3,58 +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.52 (19.08.2025) === 7 - 8 -* Changed Self-Scheduler to not show §C: shifts to Operatives, even if they are scheduled in them – this prevents “double-shifts” like §R: ODS Team 1 and §C: ODS at the same time shown 9 -* Changed Schedule to enable keyword filtering if a specific Operative is selected 10 - 11 -=== 1.8.51 (16.08.2025) === 12 - 13 -* Added counter in Schedule to calculate the hours shown in the current search / display. 14 -* Added Chinese language options and changed the “unknown” flag from EU to translingual to Operatives Management 15 - 16 -=== 1.8.50 (14.08.2025) === 17 - 18 -* Added handling of internal location URLs to L.A.S.S.I.E. Bot and Operations Status 19 -* Added Open Location to context menu for Security Operatives 20 - 21 -=== 1.8.49 (11.08.2025) === 22 - 23 -* Changed the Self-Scheduler to not show the red warning stripes for understaffed shifts if “show unassigned” is selected 24 - 25 -=== 1.8.48 (12.07.2025) === 26 - 27 -* Changed errors / warnings / messages in Operations Status about adding / removing / informing units to and from Incidents to give a clearer picture if more than one Dispatch are at work 28 -* Changed FTC client to not display warning message about pager system as it'll nearly never be there anyway 29 - 30 -=== 1.8.47 (05.07.2025) === 31 - 32 -* Bugfix: added timezone consideration to the Briefings, Items DB and Assets DB modules and the Bigscreen 33 -* Bugfix: Changed maximum field length for floor in Incident Management to 6 and changed form field to reflect maximum length 34 - 35 -=== 1.8.46 (18.06.2025) === 36 - 37 -* Changed Show Incident to include a better functionality to search for attendees in Involved and Witnesses 38 - 39 -=== 1.8.45 (14.06.2025) === 40 - 41 -* 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 …) 42 - 43 -=== 1.8.44 (06.06.2025) === 44 - 45 -* Bugfix: Various smaller spelling corrections 46 -* Changed standard Attendee CSV importer to make it more robust 47 -* Added standard Event (Schedule) CSV importer 48 -* Changed Autofill ODS-C script to accommodate for multiple parallel ODS 49 - 50 -=== 1.8.43 (14.04.2025) === 51 - 52 -* Bugfix: Correctly displaying error messages for missing Lat/Long in Location Management 53 -* Bugfix: Correctly displaying missing Nationality in Operatives Lists 54 - 55 55 === 1.8.42 (09.04.2025) === 56 56 57 -* Bugfix: Setting an Operative to INACTIVE now also sets the Access Level “No Access” 8 +* Bugfix: Setting an Operative to INACTIVE now also sets the Access Level “No Access”. 58 58 59 59 === 1.8.41 (02.04.2025) === 60 60 ... ... @@ -77,23 +77,23 @@ 77 77 78 78 === 1.8.37 (25.02.2025) === 79 79 80 -* 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 81 -* 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 31 +* 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. 32 +* 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. 82 82 83 83 === 1.8.36 (24.02.2025) === 84 84 85 -* Bugfix: debugged about a thousand bugs from Operations Status 86 -* 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 36 +* Bugfix: debugged about a thousand bugs from Operations Status. 37 +* 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. 87 87 * Changed the context menus in Operations Status to not show pager sending options when the pager system is down or unavailable 88 88 89 89 === 1.8.35 (21.02.2025) === 90 90 91 -* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC 42 +* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC. 92 92 93 93 === 1.8.34 (20.02.2025) === 94 94 95 -* Changed the complete JavaScript in Operations Status so the page is about 500% faster 96 -* 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 46 +* Changed the complete JavaScript in Operations Status so the page is about 500% faster. 47 +* 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. 97 97 98 98 === 1.8.33 (11.02.2025) === 99 99