Duplicate transaction is a very useful function, but it assumes the user wants the current date for the duplicate, which may not always be correct, especially when dealing with transactions that happened in the past. The user should be asked to enter the date for the duplicate. The ledger should be scrolled and focused on the newly entered transaction.
I don't know the relative use of duplicating a transaction for "today" vs. some previous date, but if you force the user to choose a date, you make extra work for half the cases. Currently, when you duplicate a transaction, the new one IS selected, at least in Linux. Is it not selected in Windows? If so, I'd say that is a different issue. In any case, is it really too hard to just edit the new transaction as soon as you have created it?
Of course not, I never thought about it as being too hard. It just seems fair to let the use choose the date, instead of assuming. After duplication, the new transaction is selected in Windows, too. I was not complaining about this, I was just making a note that if the user could choose a date for the duplicate, the ledger should be focused on that new transaction.
OK, so what I think would work from the UX perspective is that after duplicating a transaction, the new transaction should be shown in "Edit" mode, ideally focused on the date already. I'd agree with you that a duplicated transaction hardly ever does not need any amending.