Changes for page Changelog

Summary

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

Details

Page properties

Content

...	...	@@ -3,10 +3,183 @@
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	+
	62	+=== 1.8.40 (30.03.2025) ===
	63	+
	64	+* Bugfix: Fixed Permissions for Location Database entries
	65	+* Updated Schedule and Self-Scheduler, secured and updated POSTVAR / SQL statements
	66	+* Changed Operations Status and enabled COMBIUNITS with no scheduled Operatives
	67	+
	68	+=== 1.8.39 (20.03.2025) ===
	69	+
	70	+* Bugfix: Alerting of Dispatch for Status 9 and 5 works correctly again
	71	+
	72	+=== 1.8.38 (02.03.2025) ===
	73	+
	74	+* Added a Radio Log function for DMR calls, which can be used with a FurCom Radio Logger
	75	+* Bugfix: Fixing many bugs in CSS, surely building in more
	76	+
	77	+=== 1.8.37 (25.02.2025) ===
	78	+
	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
	81	+
	82	+=== 1.8.36 (24.02.2025) ===
	83	+
	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
	87	+
	88	+=== 1.8.35 (21.02.2025) ===
	89	+
	90	+* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC
	91	+
	92	+=== 1.8.34 (20.02.2025) ===
	93	+
	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
	96	+
	97	+=== 1.8.33 (11.02.2025) ===
	98	+
	99	+* Bugfix: Removed some bugs from Qualification Management and Event Management that occured while adding stuff in Operatives Management
	100	+
	101	+=== 1.8.32 (31.01.2025) ===
	102	+
	103	+* Added external alerts to Incident Archive list
	104	+* 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.
	105	+* Bugfix: Files are now also accepted if the extension of an allowed file type is in UPPER CASE.
	106	+
	107	+=== 1.8.31 (06.01.2025) ===
	108	+
	109	+* Changed Briefing module to not have access levels any more, since they necessarily have been "W" for everybody anyways
	110	+* Bugfix: Operative Collar IDs of C-Units in Operations Status now are correctly shown if > 999
	111	+* Bugfix: Incident Archive table now does not reset scrolling position every 15 seconds any more
	112	+* Bugfix: Operatives Duty Stats table (and others) now also scrolls header horizontally, not just content
	113	+* Changed location of several files and scripts (backend)
	114	+
	115	+=== 1.8.30 (27.12.2024) ===
	116	+
	117	+* Added direct Telegram link to most of the Telegram Handles in Operatives Management and Operatives Lists
	118	+* 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
	119	+* (((
	120	+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
	121	+)))
	122	+
	123	+=== 1.8.29 (21.12.2024) ===
	124	+
	125	+* 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
	126	+* Updated search field in Lost & Found Database to also search inside the Log Comments
	127	+* Updated table scrolling behaviour to be more mobile friendly and coherent
	128	+
	129	+=== 1.8.28 (17.12.2024) ===
	130	+
	131	+* Added an option to change all duties / events with the same title in the Schedule at the same time
	132	+
	133	+=== 1.8.27 (16.12.2024) ===
	134	+
	135	+* 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
	136	+* Added a delete option for Lost & Found images (click item to edit, then trash can next to image upload)
	137	+* Added Log comment field to Add Lost & Found item
	138	+
	139	+=== 1.8.26 (16.11.2024) ===
	140	+
	141	+* Updated ConOps Incident Management, secured and updated POSTVAR / SQL statements, added error codes and error log
	142	+* Added most of the recent features from Incident Management to ConOps Incident Management
	143	+
	144	+=== 1.8.25 (20.10.2024) ===
	145	+
	146	+* Added a module for changing Item Clearance Levels to System Settings
	147	+* Changed the Log Reports printable from Incidents to a more readable format
	148	+* Added an Incident Report to print out the whole Incident
	149	+
	150	+=== 1.8.24 (05.09.2024) ===
	151	+
	152	+* Added a System Setting to prevent Operatives un-registering from a duty in an otherwise writeable Self-Scheduler
	153	+
	154	+=== 1.8.23 (30.08.2024) ===
	155	+
	156	+* 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.
	157	+
	158	+=== 1.8.22 (29.08.2024) ===
	159	+
	160	+* Updated Self-Scheduler to include duty stats for the respective Operative
	161	+
	162	+=== 1.8.21 (27.08.2024) ===
	163	+
	164	+* 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
	165	+
	166	+=== 1.8.20 (21.08.2024) ===
	167	+
	168	+* Added a direct link to the Schedule of respective Operatives (click on the collar ID) to the Scheduler event popup
	169	+
	170	+=== 1.8.19 (11.08.2024) ===
	171	+
	172	+* Updated Operatives Duty Stats to make the table more readable. Also added EVAC as shift type.
	173	+
	174	+=== 1.8.18 (10.08.2024) ===
	175	+
	176	+* Updated the Self-Scheduler so that the buttons are better readable; also got rid of the "Save" button
	177	+
6	6	=== 1.8.17 (17.06.2024) ===
7	7
8	8	* Bugfix: All language characters can now be used for searches in Schedule and Self-Scheduler
9		-* Bugfix: Special Language characters like the ꝥ which is a þat (þ) wið a stroke, representing þat and dating back to Old Engliſh can now also be used in Schedule titles. One can alſo uſe emojis now ... why are you torturing me so much?
	181	+* Bugfix: Special unicode language characters like the ꝥ which is a þat (þ) wið a stroke, and dating back to Old Engliſh, can now also be used in Schedule titles. One can alſo uſe emojis 😸 now ... why are you torturing me so much?
	182	+* Added a searchable field for Car License Plate to Attendee DB. This can be imported from a REG DB via API or CSV.
10	10
11	11	=== 1.8.16 (14.05.2024) ===
12	12