Skip to main content
Nintex Community Menu Bar

Best Practice - Duplicate Incident Reports in Improvement Module

  • May 12, 2026
  • 1 reply
  • 21 views
B
Forum|alt.badge.img+3

Hi there,

Just curious on any suggestions on best practice when receiving duplicate incident reports in the improvements module.

For example, we currently have an incident that is under investigation/action and not yet resolved, so we are likely to continue receiving reports of the issue with examples that would assist with our currently in progress incident. 

Our thoughts to combine these would be to take a screenshot of the new report and upload it to the investigation section of the ongoing incident. Then deleting the new report as we will have all the information on this now included in the ongoing one.

Would be great to hear others thoughts.

Thanks!

    1 reply

    S
    Nintex Employee
    Forum|alt.badge.img+1
    • SwalehSunderNintex Employee
    • Nintex Employee
    • May 15, 2026

    Hi ​@bhawton 

    Great call out and appreciate you sharing how you're currently handling it!

    To be honest, there's no official guidance on this one and no way to merge incidents in the system, so there's no perfect answer here.

    That said, your approach makes total sense. Screenshotting the duplicate and uploading it to the ongoing incident keeps everything together, and deleting the duplicate keeps things tidy. Just good to know you can attach as many files as you need to an incident, so if more duplicates come in with useful info you can keep adding them to the main one.

    If a merge function is something you'd love to see, worth throwing it on the Nintex Ideas portal, that's exactly the kind of feedback that helps shape what gets built!

    Sidebar Buttons
    Nintex Community Home Contact Nintex Support Email Nintex Community Check Nintex Status
    Terms & ConditionsAccessibility statement