https://bugs.kde.org/show_bug.cgi?id=452391

            Bug ID: 452391
           Summary: ofx import account selection buttons are
                    broken/misleading
           Product: kmymoney
           Version: 5.1.2
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: importer
          Assignee: kmymoney-devel@kde.org
          Reporter: cloutier...@gmail.com
  Target Milestone: ---

SUMMARY
When importing many accounts from one ofx file, it does happen frequently that
I want to skip an account entirely. The obvious way to do that is to click on
the "skip" button. But then I get a message "You must select an account, create
a new one, or press the Abort button". Since I do have an account selected and
don’t want to create a new one, I'm left with the choice to abort. Which leads
to the question, What’s the purpose of the skip button if it only seems to be
able to trigger that warning.

Then to start being confused, clicking on abort, actually skip only one
account. I would have thought it would have cancelled the whole import. But
fine, "abort" seem to mean "skip", so I'll use that.

Finally reaching the end of my import, click on the last account "OK" and I get
a "Importing process terminated unexpectedly" error followed by an import
summary that seems to include everything and after checking and reconciliating
the imported data everything is good. So what was unexpected?


STEPS TO REPRODUCE
1. import an ofx file with many account
2. skip and abort at least one of them

OBSERVED RESULT
confusing button, popup and error

EXPECTED RESULT
- The skip button actually skip an account
- The abort button actually abort the import
- no error at the end
- no popup saying a button is useless


SOFTWARE/OS VERSIONS  archlinux
Linux/KDE Plasma: archlinux
(available in About System)
KDE Plasma Version: 5.24.2
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to