Sometimes auditors are asking to produce a full audit trail of the project. This usually happens when they cant find anything bad in the process but still have hopes to leave at least some comments/remarks. In order to resolve this, heres the complete project audit trail report: ESQL SELECT HIST.CHANGESET_ID, HIST.CHANGE_DATE, HIST.USER_NAME AS CHANGED_BY, HIST.ARTIFACT_TYPE_NAME, HIST.ARTIFACT_ID, HIST.ARTIFACT_DESC AS ARTIFACT_NAME, HIST.CHANGETYPE_NAME AS CHANGE_TYPE, HIST.SIGNATURE_HASH FROM SpiraTestEntities.R_HistoryChangeSets AS HIST WHERE HIST.PROJECT_ID = ${ProjectId} XSLT Project Audit Trail Change ID Change Date Changed By Artifact Type Artifact ID Artifact Name Change Type Signed Signed Not Signed As usual, please let me know if you find some bugs in the report. Your feedback is appreciated! en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spirateam/reports/3190.aspxthreadId=3190Vladimir Plotkin (vladimir@inmarsys.com) Sometimes auditors are asking to produce a full audit trail of the project. This usually happens when they cant find anything bad in the process but still have hopes to leave at least some comments/remarks. In order to resolve this, heres the complete project audit trail report: ESQL SELECT HIST.CHANGESET_ID, HIST.CHANGE_DATE, HIST.USER_NAME AS CHANGED_BY, HIST.ARTIFACT_TYPE_NAME, HIST.ARTIFACT_ID, HIST.ARTIFACT_DESC AS ARTIFACT_NAME, HIST.CHANGETYPE_NAME AS CHANGE_TYPE, HIST.SIGNATURE_HASH FROM SpiraTestEntities.R_HistoryChangeSets AS HIST WHERE HIST.PROJECT_ID = ${ProjectId} XSLT Project Audit Trail Change ID Change Date Changed By Artifact Type Artifact ID Artifact Name Change Type Signed Signed Not Signed As usual, please let me know if you find some bugs in the report. Your feedback is appreciated! Thu, 30 Apr 2026 09:59:22 -04002026-05-04T11:16:26-04:00/Support/Forum/spirateam/reports/3190.aspxmessageId=7623Victoria D (nino.diasamidze@inflectra.com) Hello Vlad, Excellent report, it seems that you can cover usual pain points. What I would change: 1. Add a Date Filter - it is highly recommended to add a date filter so to avoid database timeout issues due to pulling tens of thousands of rows (for large and old products). 2. Formatting the Date - currently, the CHANGE_DATE will output in Spiras raw, unformatted XML date structure (e.g., 2023-10-27T14:30:00Z). To make it look clean for the auditor, you can format it using Spiras built-in date helper, something like: Please let us know if that helped. Regards, Victoria - Fri, 01 May 2026 13:09:28 -04002026-05-01T13:09:28-04:00/Support/Forum/spirateam/reports/3190.aspx#reply7623messageId=7624Vladimir Plotkin (vladimir@inmarsys.com) Hi Victoria, Good point! The only thing is - I am not sure how to implement the date filtering. Can you help? Thanks, Vlad Fri, 01 May 2026 13:19:09 -04002026-05-01T13:19:09-04:00/Support/Forum/spirateam/reports/3190.aspx#reply7624messageId=7625Victoria D (nino.diasamidze@inflectra.com) Hello! I think it can be a basic filter in WHERE statement: WHERE HIST.PROJECT_ID = ${ProjectId} AND HIST.CHANGE_DATE >= '2026-01-01' Or use DiffDays(start_date, end_date) to make it more dynamic. Here is a practical example of using DiffDays function: https://www.inflectra.com/Support/KnowledgeBase/KB890.aspx And here you can see other options to format dates: https://www.inflectra.com/Support/KnowledgeBase/KB710.aspx Regards, Victoria - Fri, 01 May 2026 13:29:59 -04002026-05-01T13:29:59-04:00/Support/Forum/spirateam/reports/3190.aspx#reply7625messageId=7626Vladimir Plotkin (vladimir@inmarsys.com) OK, meanwhile Ive changed your suggested line to this: It produces the date/time in the following format: 2026-04-23 17:48:43 Fri, 01 May 2026 13:38:59 -04002026-05-01T13:38:59-04:00/Support/Forum/spirateam/reports/3190.aspx#reply7626messageId=7628Vladimir Plotkin (vladimir@inmarsys.com) Question: Say I want to select a date range. For this there should be a parameter on the Report page (perhaps in Custom section Filter?). Something like this: Date from: DD-MM-YYYY Date to: DD-MM-YYYY How do I introduce such filtering? Also, in case when a user wants to output everything and not bothered selecting the dates, how can I ignore the fields and output everything? Fri, 01 May 2026 14:32:03 -04002026-05-01T14:32:03-04:00/Support/Forum/spirateam/reports/3190.aspx#reply7628messageId=7630Victoria D (nino.diasamidze@inflectra.com) Hello, 1. Filtering: as you may know, there is a limitation to display 10000 rows per query. So, you will need to use a pagination in this case. Heres the solution: KB792 - How to extract large amount of artifacts from Spira using Excel or OData Regarding the filtration, you can try to use JavaScript to add a date picker on the report page, so to filter the output based on date parameters. To view the audit trail for a specific timeframe, use the Start and End dates. To view the entire history, set the Start Date to e.g. 01-Jan-2000 and the End Date to e.g. 31-Dec-2099. 2. If this is something you may need on permanent basis I would think about API & Automation Integration and consider to build a custom integration using the Spira REST API instead, so to write a small script that automatically exports the audit logs you need. Mon, 04 May 2026 11:16:26 -04002026-05-04T11:16:26-04:00/Support/Forum/spirateam/reports/3190.aspx#reply7630