Changes for page Changelog

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -3,6 +3,138 @@
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.46 (18.06.2025) ===
	7	+
	8	+* Changed Show Incident to include a better functionality to search for attendees in or witnesses
	9	+
	10	+=== 1.8.45 (14.06.2025) ===
	11	+
	12	+* 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 …)
	13	+
	14	+=== 1.8.44 (06.06.2025) ===
	15	+
	16	+* Bugfix: Various smaller spelling corrections
	17	+* Changed standard Attendee CSV importer to make it more robust
	18	+* Added standard Event (Schedule) CSV importer
	19	+* Changed Autofill ODS-C script to accommodate for multiple parallel ODS
	20	+
	21	+=== 1.8.43 (14.04.2025) ===
	22	+
	23	+* Bugfix: Correctly displaying error messages for missing Lat/Long in Location Management
	24	+* Bugfix: Correctly displaying missing Nationality in Operatives Lists
	25	+
	26	+=== 1.8.42 (09.04.2025) ===
	27	+
	28	+* Bugfix: Setting an Operative to INACTIVE now also sets the Access Level “No Access”
	29	+
	30	+=== 1.8.41 (02.04.2025) ===
	31	+
	32	+* Added standard CSV importer to Attendee Database for all clients without individual JSON API importer
	33	+
	34	+=== 1.8.40 (30.03.2025) ===
	35	+
	36	+* Bugfix: Fixed Permissions for Location Database entries
	37	+* Updated Schedule and Self-Scheduler, secured and updated POSTVAR / SQL statements
	38	+* Changed Operations Status and enabled COMBIUNITS with no scheduled Operatives
	39	+
	40	+=== 1.8.39 (20.03.2025) ===
	41	+
	42	+* Bugfix: Alerting of Dispatch for Status 9 and 5 works correctly again
	43	+
	44	+=== 1.8.38 (02.03.2025) ===
	45	+
	46	+* Added a Radio Log function for DMR calls, which can be used with a FurCom Radio Logger
	47	+* Bugfix: Fixing many bugs in CSS, surely building in more
	48	+
	49	+=== 1.8.37 (25.02.2025) ===
	50	+
	51	+* 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
	52	+* 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
	53	+
	54	+=== 1.8.36 (24.02.2025) ===
	55	+
	56	+* Bugfix: debugged about a thousand bugs from Operations Status
	57	+* 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
	58	+* Changed the context menus in Operations Status to not show pager sending options when the pager system is down or unavailable
	59	+
	60	+=== 1.8.35 (21.02.2025) ===
	61	+
	62	+* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC
	63	+
	64	+=== 1.8.34 (20.02.2025) ===
	65	+
	66	+* Changed the complete JavaScript in Operations Status so the page is about 500% faster
	67	+* 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
	68	+
	69	+=== 1.8.33 (11.02.2025) ===
	70	+
	71	+* Bugfix: Removed some bugs from Qualification Management and Event Management that occured while adding stuff in Operatives Management
	72	+
	73	+=== 1.8.32 (31.01.2025) ===
	74	+
	75	+* Added external alerts to Incident Archive list
	76	+* Bugfix: Lost & Found and Item Database now also accepts photos via L.A.S.S.I.E. Bot if they are of rather low resolution.
	77	+* Bugfix: Files are now also accepted if the extension of an allowed file type is in UPPER CASE.
	78	+
	79	+=== 1.8.31 (06.01.2025) ===
	80	+
	81	+* Changed Briefing module to not have access levels any more, since they necessarily have been "W" for everybody anyways
	82	+* Bugfix: Operative Collar IDs of C-Units in Operations Status now are correctly shown if > 999
	83	+* Bugfix: Incident Archive table now does not reset scrolling position every 15 seconds any more
	84	+* Bugfix: Operatives Duty Stats table (and others) now also scrolls header horizontally, not just content
	85	+* Changed location of several files and scripts (backend)
	86	+
	87	+=== 1.8.30 (27.12.2024) ===
	88	+
	89	+* Added direct Telegram link to most of the Telegram Handles in Operatives Management and Operatives Lists
	90	+* Added an upload function for training certificates to Qualification & Training in Operatives Management; the qualification types First Aider, EMT / Paramedic, 34a, SiA, Firefighter and M.D. will require a certificate to be uploaded upon adding or changing them
	91	+* (((
	92	+Changed the add and change form for the qualification types First Aider, EMT / Paramedic and Firefighter in Qualification & Training in Operatives Management to account for standard training levels
	93	+)))
	94	+
	95	+=== 1.8.29 (21.12.2024) ===
	96	+
	97	+* Added autocomplete for the Item Type in Lost & Found Database – it will display the types from all lost or found items, but not the returned ones
	98	+* Updated search field in Lost & Found Database to also search inside the Log Comments
	99	+* Updated table scrolling behaviour to be more mobile friendly and coherent
	100	+
	101	+=== 1.8.28 (17.12.2024) ===
	102	+
	103	+* Added an option to change all duties / events with the same title in the Schedule at the same time
	104	+
	105	+=== 1.8.27 (16.12.2024) ===
	106	+
	107	+* Added options to only show one particular status to Lost & Found Database which should make it more easy to display items reported as lost only
	108	+* Added a delete option for Lost & Found images (click item to edit, then trash can next to image upload)
	109	+* Added Log comment field to Add Lost & Found item
	110	+
	111	+=== 1.8.26 (16.11.2024) ===
	112	+
	113	+* Updated ConOps Incident Management, secured and updated POSTVAR / SQL statements, added error codes and error log
	114	+* Added most of the recent features from Incident Management to ConOps Incident Management
	115	+
	116	+=== 1.8.25 (20.10.2024) ===
	117	+
	118	+* Added a module for changing Item Clearance Levels to System Settings
	119	+* Changed the Log Reports printable from Incidents to a more readable format
	120	+* Added an Incident Report to print out the whole Incident
	121	+
	122	+=== 1.8.24 (05.09.2024) ===
	123	+
	124	+* Added a System Setting to prevent Operatives un-registering from a duty in an otherwise writeable Self-Scheduler
	125	+
	126	+=== 1.8.23 (30.08.2024) ===
	127	+
	128	+* Added a FAQ system for L.A.S.S.I.E. Bot  to answer questions in a non-PM Telegram chat with the word "tell" as trigger if directly addressed (e.g.: "@LassieBot tell me about Tuesday"). Answer keywords and answers can be set in System Settings → Bot FAQ Answers. The Telegram chat IDs, which the bot shall answer questions for any convention in, have to be set as comma separated list in System Settings → Settings → Group IDs of L.A.S.S.I.E. Bot FAQ System.
	129	+
	130	+=== 1.8.22 (29.08.2024) ===
	131	+
	132	+* Updated Self-Scheduler to include duty stats for the respective Operative
	133	+
	134	+=== 1.8.21 (27.08.2024) ===
	135	+
	136	+* Updated Schedule to also send information about //what// has changed to scheduled Operatives on change of the content of a schedule item via L.A.S.S.I.E. Bot
	137	+
6	6	=== 1.8.20 (21.08.2024) ===
7	7
8	8	* Added a direct link to the Schedule of respective Operatives (click on the collar ID) to the Scheduler event popup