ledgersmb/LedgerSMB

Unexpected behaviour copying a REVERSING transaction

Closed this issue · 1 comments

ehuelsmann commented

Version

1.11.12

What browsers are you seeing the problem on?

This problem isn't browser related

What happened?

When copying a REVERSING transaction, the copied transaction indicates it will reverse the same transaction as the transaction that was copied from. However, a transaction can't be reversed twice, so this is clearly incorrect behaviour.

What should have happened?

We need to determine that either

  1. Copying a REVERSING transaction doesn't make sense
  2. Copying a REVERSING transaction makes it a normal transaction
ehuelsmann commented

Ok. I decided that copying a reversing transaction simply shouldn't be allowed. That's the quickest and most predictable outcome (for AR and AP transactions/invoices).