Kenn Sippell
Kenn Sippell
Removing from 3.12 pending admin console design conversations.
Probably completion date of last purge (or maybe last 3 purges since the purge schedule can be anything?) and we need the full content of all `purgelog:error` documents.
Sounding the alarm is a nice first step, but it isn't the whole picture. Once the alarm is sounded, the user landscape is a bit more complex. Currently to get...
As of 3.14, I believe purgelog:error happens even when purging completes successfully. So we might need to clarify the idea of how/when we "sound the alarm". I'm not sure it...
Sorry, I'm just starting to use 3.14 now. I thought there was a `purgelog:error` for each contact that failed to purge. But it is a new attribute `skipped_contacts` inside the...
I've never actually seen a purgelog:error - maybe we don't need them at all. So maybe something like: ``` { "purging": { "latest": { "success": "2022-02-02....", "failure": "2022-01-01....", "skipped_contacts": ["mr_a",...
There are about 100 feedback docs/month due to this bug for production PiH instance.
Is it possible to split this issue into two? 1. Convert JSON to XML and stop attaching the XML to new reports. 1. Perform the migration to remove the attachment...
So if we are just converting JSON to XML and not attaching the XML to new reports, is this regarded as a breaking change?
Curious - after getting this fix via an upgrade to 4.0, would projects be able to remove attachments from the reports created via 3.x versions without breaking anything?