Changes for page Changelog

Last modified by Treyfane Dingo on 2025/08/19 22:33

From version 133.1
edited by Treyfane Dingo
on 2025/03/30 14:46
Change comment: There is no comment for this version
To version 145.2
edited by Treyfane Dingo
on 2025/08/19 21:16
Change comment: There is no comment for this version

Summary

Details

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