Changes for page Changelog
Last modified by Treyfane Dingo on 2025/04/14 17:12
From version 113.1
edited by Treyfane Dingo
on 2024/12/20 23:56
on 2024/12/20 23:56
Change comment:
There is no comment for this version
To version 92.1
edited by Treyfane Dingo
on 2024/06/17 21:56
on 2024/06/17 21:56
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -3,64 +3,10 @@ 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.29 (21.12.2024) === 7 - 8 -* 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 9 -* Updated search field in Lost & Found Database to also search inside the Log Comments 10 - 11 -=== 1.8.28 (17.12.2024) === 12 - 13 -* Added an option to change all duties / events with the same title in the Schedule at the same time 14 - 15 -=== 1.8.27 (16.12.2024) === 16 - 17 -* 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 18 -* Added a delete option for Lost & Found images (click item to edit, then trash can next to image upload) 19 -* Added Log comment field to Add Lost & Found item 20 - 21 -=== 1.8.26 (16.11.2024) === 22 - 23 -* Updated ConOps Incident Management, secured and updated POSTVAR / SQL statements, added error codes and error log 24 -* Added most of the recent features from Incident Management to ConOps Incident Management 25 - 26 -=== 1.8.25 (20.10.2024) === 27 - 28 -* Added a module for changing Item Clearance Levels to System Settings 29 -* Changed the Log Reports printable from Incidents to a more readable format 30 -* Added an Incident Report to print out the whole Incident 31 - 32 -=== 1.8.24 (05.09.2024) === 33 - 34 -* Added a System Setting to prevent Operatives un-registering from a duty in an otherwise writeable Self-Scheduler 35 - 36 -=== 1.8.23 (30.08.2024) === 37 - 38 -* 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. 39 - 40 -=== 1.8.22 (29.08.2024) === 41 - 42 -* Updated Self-Scheduler to include duty stats for the respective Operative 43 - 44 -=== 1.8.21 (27.08.2024) === 45 - 46 -* 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 47 - 48 -=== 1.8.20 (21.08.2024) === 49 - 50 -* Added a direct link to the Schedule of respective Operatives (click on the collar ID) to the Scheduler event popup 51 - 52 -=== 1.8.19 (11.08.2024) === 53 - 54 -* Updated Operatives Duty Stats to make the table more readable. Also added EVAC as shift type. 55 - 56 -=== 1.8.18 (10.08.2024) === 57 - 58 -* Updated the Self-Scheduler so that the buttons are better readable; also got rid of the "Save" button 59 - 60 60 === 1.8.17 (17.06.2024) === 61 61 62 62 * Bugfix: All language characters can now be used for searches in Schedule and Self-Scheduler 63 -* 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?9 +* 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? 64 64 * Added a searchable field for Car License Plate to Attendee DB. This can be imported from a REG DB via API or CSV. 65 65 66 66 === 1.8.16 (14.05.2024) ===