Changes for page Changelog

Last modified by Treyfane Dingo on 2025/08/16 12:36

From version 145.1
edited by Treyfane Dingo
on 2025/08/16 12:36
Change comment: There is no comment for this version
To version 134.1
edited by Treyfane Dingo
on 2025/04/01 21:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,54 +3,6 @@
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.51 (16.08.2025) ===
7 -
8 -* Added counter in Schedule to calculate the hours shown in the current search / display.
9 -* Added Chinese language options and changed the “unknown” flag from EU to translingual to Operatives Management
10 -
11 -=== 1.8.50 (14.08.2025) ===
12 -
13 -* Added handling of internal location URLs to L.A.S.S.I.E. Bot and Operations Status
14 -* Added Open Location to context menu for Security Operatives
15 -
16 -=== 1.8.49 (11.08.2025) ===
17 -
18 -* Changed the Self-Scheduler to not show the red warning stripes for understaffed shifts if “show unassigned” is selected
19 -
20 -=== 1.8.48 (12.07.2025) ===
21 -
22 -* 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
23 -* Changed FTC client to not display warning message about pager system as it'll nearly never be there anyway
24 -
25 -=== 1.8.47 (05.07.2025) ===
26 -
27 -* Bugfix: added timezone consideration to the Briefings, Items DB and Assets DB modules and the Bigscreen
28 -* Bugfix: Changed maximum field length for floor in Incident Management to 6 and changed form field to reflect maximum length
29 -
30 -=== 1.8.46 (18.06.2025) ===
31 -
32 -* Changed Show Incident to include a better functionality to search for attendees in Involved and Witnesses
33 -
34 -=== 1.8.45 (14.06.2025) ===
35 -
36 -* 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 …)
37 -
38 -=== 1.8.44 (06.06.2025) ===
39 -
40 -* Bugfix: Various smaller spelling corrections
41 -* Changed standard Attendee CSV importer to make it more robust
42 -* Added standard Event (Schedule) CSV importer
43 -* Changed Autofill ODS-C script to accommodate for multiple parallel ODS
44 -
45 -=== 1.8.43 (14.04.2025) ===
46 -
47 -* Bugfix: Correctly displaying error messages for missing Lat/Long in Location Management
48 -* Bugfix: Correctly displaying missing Nationality in Operatives Lists
49 -
50 -=== 1.8.42 (09.04.2025) ===
51 -
52 -* Bugfix: Setting an Operative to INACTIVE now also sets the Access Level “No Access”
53 -
54 54  === 1.8.41 (02.04.2025) ===
55 55  
56 56  * Added standard CSV importer to Attendee Database for all clients without individual JSON API importer
... ... @@ -72,23 +72,23 @@
72 72  
73 73  === 1.8.37 (25.02.2025) ===
74 74  
75 -* 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
76 -* 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
27 +* 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.
28 +* 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.
77 77  
78 78  === 1.8.36 (24.02.2025) ===
79 79  
80 -* Bugfix: debugged about a thousand bugs from Operations Status
81 -* 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
82 -* Changed the context menus in Operations Status to not show pager sending options when the pager system is down or unavailable
32 +* Bugfix: debugged about a thousand bugs from Operations Status.
33 +* 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.
34 +* Changed the context menus in Operations Status to not show pager sending options when the pager system is down or unavailable.
83 83  
84 84  === 1.8.35 (21.02.2025) ===
85 85  
86 -* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC
38 +* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC.
87 87  
88 88  === 1.8.34 (20.02.2025) ===
89 89  
90 -* Changed the complete JavaScript in Operations Status so the page is about 500% faster
91 -* 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
42 +* Changed the complete JavaScript in Operations Status so the page is about 500% faster.
43 +* 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.
92 92  
93 93  === 1.8.33 (11.02.2025) ===
94 94