Back to bug 32057

Who When What Removed Added
kyle 2022-11-01 10:35:11 UTC Assignee koha-bugs kyle
kyle 2022-11-01 10:51:17 UTC Status NEW Needs Signoff
kyle 2022-11-01 11:04:22 UTC Attachment #142855 Attachment is obsolete 0 1
kyle 2022-11-01 11:06:02 UTC Patch complexity --- Small patch
david 2022-12-20 01:58:01 UTC CC david
Status Needs Signoff Patch doesn't apply
kyle 2022-12-20 14:15:58 UTC Status Patch doesn't apply Needs Signoff
kyle 2022-12-20 14:16:02 UTC Attachment #142857 Attachment is obsolete 0 1
kyle 2022-12-20 14:21:51 UTC Attachment #144734 Attachment is obsolete 0 1
kyle 2022-12-20 14:22:57 UTC Attachment #144736 Attachment is obsolete 0 1
kyle 2022-12-20 14:24:07 UTC Attachment #144737 Attachment is obsolete 0 1
david 2022-12-20 22:00:05 UTC Status Needs Signoff Failed QA
kyle 2022-12-21 14:48:56 UTC Status Failed QA Needs Signoff
david 2022-12-21 17:41:35 UTC Status Needs Signoff Signed Off
david 2022-12-21 17:41:40 UTC Attachment #144735 Attachment is obsolete 0 1
david 2022-12-21 17:41:45 UTC Attachment #144738 Attachment is obsolete 0 1
david 2022-12-21 17:41:51 UTC Attachment #144769 Attachment is obsolete 0 1
david 2022-12-21 17:42:26 UTC Comment 10 Tag obsolete
david 2022-12-21 17:42:38 UTC Comment 9 Tag obsolete
david 2022-12-21 17:42:44 UTC Comment 8 Tag obsolete
david 2022-12-21 17:42:49 UTC Comment 7 Tag obsolete
david 2022-12-21 17:42:55 UTC Comment 6 Tag obsolete
david 2022-12-21 17:43:01 UTC Comment 5 Tag obsolete
david 2022-12-21 17:43:07 UTC Comment 4 Tag obsolete
david 2022-12-21 17:43:14 UTC Comment 3 Tag obsolete
david 2022-12-21 17:43:19 UTC Comment 2 Tag obsolete
david 2022-12-21 17:43:26 UTC Comment 1 Tag obsolete
david 2022-12-21 18:01:35 UTC Text to go in the release notes It can be useful to know where in Koha a particular logged action was generated from, and how his enhancement adds stack traces to action logs. To use, add a number for the trace depth (such as 3) to the new system preference ActionLogsTraceDepth. The details for the stack trace are available by querying the database, for example: SELECT * FROM action_logs WHERE trace IS NOT NULL;
david 2022-12-21 18:02:22 UTC Text to go in the release notes It can be useful to know where in Koha a particular logged action was generated from, and how his enhancement adds stack traces to action logs. To use, add a number for the trace depth (such as 3) to the new system preference ActionLogsTraceDepth. The details for the stack trace are available by querying the database, for example: SELECT * FROM action_logs WHERE trace IS NOT NULL; It can be useful to know where in Koha a logged action was generated from, and how. This enhancement adds stack traces to action logs. To use, add a number for the trace depth (such as 3) to the new system preference ActionLogsTraceDepth. The details for the stack trace are available by querying the database, for example: SELECT * FROM action_logs WHERE trace IS NOT NULL;
m.de.rooy 2023-02-17 10:55:37 UTC CC m.de.rooy
m.de.rooy 2023-02-17 10:56:04 UTC QA Contact testopia m.de.rooy
m.de.rooy 2023-02-22 13:56:03 UTC Status Signed Off Passed QA
m.de.rooy 2023-02-22 13:56:06 UTC Attachment #144786 Attachment is obsolete 0 1
m.de.rooy 2023-02-22 13:56:08 UTC Attachment #144787 Attachment is obsolete 0 1
m.de.rooy 2023-02-22 13:56:10 UTC Attachment #144788 Attachment is obsolete 0 1
tomascohen 2023-03-14 12:10:24 UTC Version(s) released in 23.05.00
Status Passed QA Pushed to master
m.de.rooy 2023-03-14 12:33:25 UTC Keywords additional_work_needed
m.de.rooy 2023-03-14 12:34:11 UTC CC tomascohen
tomascohen 2023-03-14 13:56:32 UTC Keywords additional_work_needed
matt.blenkinsop 2023-03-17 17:26:11 UTC CC matt.blenkinsop
Status Pushed to master Needs documenting
caroline.cyr-la-rose 2023-05-12 13:54:04 UTC Status Needs documenting RESOLVED
Documentation contact Caroline Cyr La Rose
Documentation submission https://gitlab.com/koha-community/koha-manual/-/merge_requests/683
CC caroline.cyr-la-rose
Resolution --- FIXED
katrin.fischer 2023-05-18 14:07:29 UTC Text to go in the release notes It can be useful to know where in Koha a logged action was generated from, and how. This enhancement adds stack traces to action logs. To use, add a number for the trace depth (such as 3) to the new system preference ActionLogsTraceDepth. The details for the stack trace are available by querying the database, for example: SELECT * FROM action_logs WHERE trace IS NOT NULL; It can be useful to know where in Koha a logged action was generated from, and how. This enhancement adds stack traces to action logs. To use, add a number for the trace depth (such as 3) to the new system preference `ActionLogsTraceDepth`. The details for the stack trace are available by querying the database, for example:
`SELECT * FROM action_logs WHERE trace IS NOT NULL;`
Component Architecture, internals, and plumbing Reports
katrin.fischer 2023-12-28 20:43:11 UTC Status RESOLVED CLOSED

Back to bug 32057