Skip to Content

Changes for page Changelog

Last modified by Treyfane Dingo on 2025/11/09 22:15
From version 152.2
edited by Treyfane Dingo
on 2025/10/04 22:08
Change comment: There is no comment for this version
To version 134.2
edited by Treyfane Dingo
on 2025/04/09 16:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,77 +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.56 (01.10.2025) ===
7 -
8 -* Changed Self-Scheduler so shifts that overlap with already selected shifts and back-to-back shifts at different locations are hid—preventing double-booking and ensuring realistic handovers/travel time.
9 -
10 -=== 1.8.55 (29.09.2025) ===
11 -
12 -* Changed Schedule and Self-Scheduler so a change of the Options will not reset the selected calendar view (week/day) any more
13 -
14 -=== 1.8.54 (18.09.2025) ===
15 -
16 -* Bugfix: Having an individual RIC but no configured POCSAG transmitter now does not throw a Javascript error in Operation Status any more
17 -* Bugfix: Sending several individual Telegram / Pager messages in Operation Status in a row now sends several individual messages … and not the same one over and over
18 -
19 -=== 1.8.53 (28.08.2025) ===
20 -
21 -* Changed Column names in PNG Database to better reflect the placeholders for letters
22 -
23 -=== 1.8.52 (19.08.2025) ===
24 -
25 -* 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
26 -* Changed Schedule to enable keyword filtering if a specific Operative is selected
27 -* Bugfix: counter in Schedule counted events over daybreak twice – no not more
28 -* Added Operative duty hours count to counter in Schedule if Operative is selected
29 -
30 -=== 1.8.51 (16.08.2025) ===
31 -
32 -* Added counter in Schedule to calculate the hours shown in the current search / display.
33 -* Added Chinese language options and changed the “unknown” flag from EU to translingual to Operatives Management
34 -
35 -=== 1.8.50 (14.08.2025) ===
36 -
37 -* Added handling of internal location URLs to L.A.S.S.I.E. Bot and Operations Status
38 -* Added Open Location to context menu for Security Operatives
39 -
40 -=== 1.8.49 (11.08.2025) ===
41 -
42 -* Changed the Self-Scheduler to not show the red warning stripes for understaffed shifts if “show unassigned” is selected
43 -
44 -=== 1.8.48 (12.07.2025) ===
45 -
46 -* 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
47 -* Changed FTC client to not display warning message about pager system as it'll nearly never be there anyway
48 -
49 -=== 1.8.47 (05.07.2025) ===
50 -
51 -* Bugfix: added timezone consideration to the Briefings, Items DB and Assets DB modules and the Bigscreen
52 -* Bugfix: Changed maximum field length for floor in Incident Management to 6 and changed form field to reflect maximum length
53 -
54 -=== 1.8.46 (18.06.2025) ===
55 -
56 -* Changed Show Incident to include a better functionality to search for attendees in Involved and Witnesses
57 -
58 -=== 1.8.45 (14.06.2025) ===
59 -
60 -* 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 …)
61 -
62 -=== 1.8.44 (06.06.2025) ===
63 -
64 -* Bugfix: Various smaller spelling corrections
65 -* Changed standard Attendee CSV importer to make it more robust
66 -* Added standard Event (Schedule) CSV importer
67 -* Changed Autofill ODS-C script to accommodate for multiple parallel ODS
68 -
69 -=== 1.8.43 (14.04.2025) ===
70 -
71 -* Bugfix: Correctly displaying error messages for missing Lat/Long in Location Management
72 -* Bugfix: Correctly displaying missing Nationality in Operatives Lists
73 -
74 74  === 1.8.42 (09.04.2025) ===
75 75  
76 -* 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”.
77 77  
78 78  === 1.8.41 (02.04.2025) ===
79 79  
... ... @@ -96,23 +96,23 @@
96 96  
97 97  === 1.8.37 (25.02.2025) ===
98 98  
99 -* 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
100 -* 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.
101 101  
102 102  === 1.8.36 (24.02.2025) ===
103 103  
104 -* Bugfix: debugged about a thousand bugs from Operations Status
105 -* 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.
106 106  * Changed the context menus in Operations Status to not show pager sending options when the pager system is down or unavailable
107 107  
108 108  === 1.8.35 (21.02.2025) ===
109 109  
110 -* 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.
111 111  
112 112  === 1.8.34 (20.02.2025) ===
113 113  
114 -* Changed the complete JavaScript in Operations Status so the page is about 500% faster
115 -* 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.
116 116  
117 117  === 1.8.33 (11.02.2025) ===
118 118