Description
Problem description
Client audits can include columns that identify the user making changes and the reason they've made changes.
These are not included in the known header values used to build audit exports and are not saved to the database.
This means the only way to access these audit events is to manually/programatically download each submission's audit attachment. It's not possible to use the submission export because all audit files have filename audit.csv and stack.
Reported by @chrissyhroberts in Slack
URL of the page
Steps to reproduce the problem
Use a form like this one that identifies user and tracks change reasons. Fill out the form in Collect, making sure to save a draft, reopen, change a value so that you can enter a change reason.
Screenshot
Expected behavior
user and change-reason columns are included in export.
Central version shown in version.txt
Browser version
Around when did you see the problem (in UTC)?
Other notes (if any)
Metadata
Metada 4A52 ta
Assignees
Type
Projects
Status
✅ done