https://bugs.kde.org/show_bug.cgi?id=393037
--- Comment #5 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular b
https://bugs.kde.org/show_bug.cgi?id=391982
--- Comment #2 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular b
https://bugs.kde.org/show_bug.cgi?id=391932
--- Comment #17 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=343291
--- Comment #11 from Leslie Brothers ---
Jack,
You referenced a typo in your message. I may have been reading too
quickly but I thought you meant my date of an entry, 1959, might have
been a typo. Indeed, it was. So I was saying, yes, it was a typo
https://bugs.kde.org/show_bug.cgi?id=343291
--- Comment #10 from Jack ---
Yes, the consistency check continues to be improved to identify more and more
different issues.
However, what typo? If it's in my message, I plead too much hurry. If it's in
the program, we can fix it.
--
You are receiv
https://bugs.kde.org/show_bug.cgi?id=343291
--- Comment #9 from Leslie Brothers ---
Dear Jack,
Hello and thank you for this follow up on the bug I initially reported
in 2015.
In more recent versions of KMM I saw this anomalous entry reported (a
typo!) in the consistency check and I have fixed the
https://bugs.kde.org/show_bug.cgi?id=396301
Jack changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=396301
Jon changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Version|5.0.1 |
https://bugs.kde.org/show_bug.cgi?id=462246
--- Comment #2 from Jesse ---
Hi Jack,
Hoping that replying on my phone gets to you. Will check later.
Suggestion for implementation: what about tagging those "ghost" transactions
with a new status code "S" for Scheduled to go along with Cleared and
Re
https://bugs.kde.org/show_bug.cgi?id=384804
Jack changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Severity|normal
https://bugs.kde.org/show_bug.cgi?id=462246
--- Comment #1 from Jack ---
This is a valid wishlist. The underlying issue is that scheduled transactions
in the future are not really transactions until they are entered into the
ledger. They are shown in the ledger due to special handling which is
https://bugs.kde.org/show_bug.cgi?id=343291
Jack changed:
What|Removed |Added
CC|ostroffjh@users.sourceforge |
|.net|
--- C
https://bugs.kde.org/show_bug.cgi?id=462513
Jack changed:
What|Removed |Added
CC|ostroffjh@users.sourceforge |
|.net|
--- C
https://bugs.kde.org/show_bug.cgi?id=462513
--- Comment #2 from KB.claim ---
Thanks Jack for the info & the graceful reception of the comments related to
documentation.
I will try to support hands on with the documentation once I know more of
kMyMoney. Is the documentation available as source, to
14 matches
Mail list logo
