Skip to Content

Changes for page Changelog

Last modified by Treyfane Dingo on 2025/08/19 22:33
From version 143.1
edited by Treyfane Dingo
on 2025/08/11 16:47
Change comment: There is no comment for this version
To version 128.2
edited by Treyfane Dingo
on 2025/02/25 03:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,82 +3,24 @@
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.49 (11.08.2025) ===
6 +=== 1.9.0 (25.02.2025) ===
7 7  
8 -* Changed the Self-Scheduler to not show the red warning stripes for understaffed shifts if “show unassigned” is selected
8 +* Added a whole new location mapping system to Incident Management which makes use of OpenStreetMaps and can make use of a C3Nav
9 9  
10 -=== 1.8.48 (12.07.2025) ===
11 -
12 -* 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
13 -* Changed FTC client to not display warning message about pager system as it'll nearly never be there anyway
14 -
15 -=== 1.8.47 (05.07.2025) ===
16 -
17 -* Bugfix: added timezone consideration to the Briefings, Items DB and Assets DB modules and the Bigscreen
18 -* Bugfix: Changed maximum field length for floor in Incident Management to 6 and changed form field to reflect maximum length
19 -
20 -=== 1.8.46 (18.06.2025) ===
21 -
22 -* Changed Show Incident to include a better functionality to search for attendees in Involved and Witnesses
23 -
24 -=== 1.8.45 (14.06.2025) ===
25 -
26 -* 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 …)
27 -
28 -=== 1.8.44 (06.06.2025) ===
29 -
30 -* Bugfix: Various smaller spelling corrections
31 -* Changed standard Attendee CSV importer to make it more robust
32 -* Added standard Event (Schedule) CSV importer
33 -* Changed Autofill ODS-C script to accommodate for multiple parallel ODS
34 -
35 -=== 1.8.43 (14.04.2025) ===
36 -
37 -* Bugfix: Correctly displaying error messages for missing Lat/Long in Location Management
38 -* Bugfix: Correctly displaying missing Nationality in Operatives Lists
39 -
40 -=== 1.8.42 (09.04.2025) ===
41 -
42 -* Bugfix: Setting an Operative to INACTIVE now also sets the Access Level “No Access”
43 -
44 -=== 1.8.41 (02.04.2025) ===
45 -
46 -* Added standard CSV importer to Attendee Database for all clients without individual JSON API importer
47 -
48 -=== 1.8.40 (30.03.2025) ===
49 -
50 -* Bugfix: Fixed Permissions for Location Database entries
51 -* Updated Schedule and Self-Scheduler, secured and updated POSTVAR / SQL statements
52 -* Changed Operations Status and enabled COMBIUNITS with no scheduled Operatives
53 -
54 -=== 1.8.39 (20.03.2025) ===
55 -
56 -* Bugfix: Alerting of Dispatch for Status 9 and 5 works correctly again
57 -
58 -=== 1.8.38 (02.03.2025) ===
59 -
60 -* Added a Radio Log function for DMR calls, which can be used with a FurCom Radio Logger
61 -* Bugfix: Fixing many bugs in CSS, surely building in more
62 -
63 -=== 1.8.37 (25.02.2025) ===
64 -
65 -* 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
66 -* 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
67 -
68 68  === 1.8.36 (24.02.2025) ===
69 69  
70 -* Bugfix: debugged about a thousand bugs from Operations Status
71 -* 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
72 -* Changed the context menus in Operations Status to not show pager sending options when the pager system is down or unavailable
12 +* Bugfix: debugged about a thousand bugs from Operations Status.
13 +* 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.
14 +* Changed the context menus in Operations Status to not show pager sending options when the pager system is down or unavailable.
73 73  
74 74  === 1.8.35 (21.02.2025) ===
75 75  
76 -* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC
18 +* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC.
77 77  
78 78  === 1.8.34 (20.02.2025) ===
79 79  
80 -* Changed the complete JavaScript in Operations Status so the page is about 500% faster
81 -* 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
22 +* Changed the complete JavaScript in Operations Status so the page is about 500% faster.
23 +* 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.
82 82  
83 83  === 1.8.33 (11.02.2025) ===
84 84