Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 2 Next »

[awaiting a good template!]

Quick list

  • Solution does not accurately identify dependencies and therefore imports don’t import all data correctly - use a POC, structured testing

  • Project team doesn’t consult widely enough with the Mautic community therefore requirements and/or functions critical to the success of the project are omitted - publish regular updates, decision and risk log, make them public

  • Complexities in creating the feature are not uncovered until too late in the process - use a POC

  • Data may get corrupted during import/export due to format mismatches, incomplete files, or interruptions - use standard file formats eg JSON; check for validity as a step; where possible implement an undo function

  • Large import/export operations might slow down the system or cause timeouts - use an analysis function to stop import at more than X entities or break down into chunks; Use asynchronous processes with progress tracking to avoid blocking the UI.

  • Imports may create duplicate entries, leading to data inconsistencies; Implement duplicate detection and merging logic (e.g., match on email or unique identifier). Offer configurable deduplication rules to users. Notify users of potential duplicates during import.

  • Sensitive data may be exposed or manipulated during export or through maliciously crafted imports. Don't allow the export of any sensitive data eg email addresses and contacts; note all successful actions in the Mautic audit log

  • Users may attempt to import/export files in unsupported or incorrectly formatted file types. Clearly specify the filetype required in the UI; Check for filetype and format up front on import, encourage users to only user files exported from Mautic.

  • Misalignment with Mautic configurations. Import/export may conflict with existing workflows, campaigns, or custom fields. Validate imported data against Mautic's configuration (e.g., required fields, campaign dependencies). Structured testing prior to production release.

  • New hires don’t have good enough understanding of the product - support them well, do regular reviews, keep work visible

  • No labels