Importing contribution with same transaction id as an existing contribution hijacks the initial contribution
- Create a contribution.
- Give it a trxn id, or note the trxn id if it was automatic.
- Do a contribution import, choosing to insert new records, where you make the trxn id in the file the same as the one just created, and with some different particulars.
- Notice that the contribution with that transaction id has now moved to whatever contact was in your import file, and the details updated.
What I would expect is that it says it's a duplicate and doesn't import it.
Edited since originally it came up with a recurring contribution but it applies to all.