Re: [kmymoney] [Bug 421288] Unable to delete some categories
Should we maybe leave the option enabled at all times but show appropriate message with explanation of impossible to delete? I too had a similar problem with deleting my investment accounts that had securities configured, the first time I used that functionality in kmymoney. On Sun, May 10, 2020 at 1:15 PM Thomas Baumgart wrote: > https://bugs.kde.org/show_bug.cgi?id=421288 > > --- Comment #3 from Thomas Baumgart --- > The following items are not checked for references when the deletion is > disabled for categories: > > - Transactions > - Accounts/Categories > - Schedules > - Budgets > > This would leave reports as a candidate if you ask me. > > -- > You are receiving this mail because: > You are the assignee for the bug.
[kmymoney] [Bug 421288] Unable to delete some categories
https://bugs.kde.org/show_bug.cgi?id=421288 --- Comment #4 from Dawid Wróbel --- Should we maybe leave the option enabled at all times but show appropriate message with explanation of impossible to delete? I too had a similar problem with deleting my investment accounts that had securities configured, the first time I used that functionality in kmymoney. On Sun, May 10, 2020 at 1:15 PM Thomas Baumgart wrote: > https://bugs.kde.org/show_bug.cgi?id=421288 > > --- Comment #3 from Thomas Baumgart --- > The following items are not checked for references when the deletion is > disabled for categories: > > - Transactions > - Accounts/Categories > - Schedules > - Budgets > > This would leave reports as a candidate if you ask me. > > -- > You are receiving this mail because: > You are the assignee for the bug. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 421307] New: Account context menu's Reconcile option opens incorrect ledger
https://bugs.kde.org/show_bug.cgi?id=421307 Bug ID: 421307 Summary: Account context menu's Reconcile option opens incorrect ledger Product: kmymoney Version: git (master) Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-devel@kde.org Reporter: dev.rszczes...@gmail.com Target Milestone: --- SUMMARY Selecting the 'Reconcile...' option from account's context menu in the Accounts view opens ledger of the last account viewed in the Ledgers view, not of the account selected in the Accounts view. STEPS TO REPRODUCE 1. Go to the Ledgers view and select any account from the drop-down list at the top. Let's call it Account A. 2. Go to the Accounts view and right-click any user-defined account other than Account A. Let's call it Account B. 3. Select the 'Reconcile...' option from the context menu. OBSERVED RESULT Reconciliation Wizard starts on top of the Ledgers view. The acount selected in the drop-down list is still Account A. EXPECTED RESULT The reconciliation process should start for Account B selected in the Accounts view instead of Account A previously viewed in the Ledgers view. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 421288] Unable to delete some categories
https://bugs.kde.org/show_bug.cgi?id=421288 --- Comment #3 from Thomas Baumgart --- The following items are not checked for references when the deletion is disabled for categories: - Transactions - Accounts/Categories - Schedules - Budgets This would leave reports as a candidate if you ask me. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 421288] Unable to delete some categories
https://bugs.kde.org/show_bug.cgi?id=421288 bren...@coupeware.com changed: What|Removed |Added CC||bren...@coupeware.com --- Comment #2 from bren...@coupeware.com --- Are they be used in scheduled transactions? Would that stop them from being deleted? -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 421288] Unable to delete some categories
https://bugs.kde.org/show_bug.cgi?id=421288 --- Comment #1 from Jack --- Having transactions does not prevent deletion of a category, because you will then be asked what other category those transactions should be assigned to. I wonder if those categories you can't delete are closed (they are actually accounts) but I can't find any way in the program to open or close category accounts, so I don't know how it could have happened. Can you provide a sample kmy file? Perhaps save your file anonymized, and confirm it still shows the same problem? -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 421288] New: Unable to delete some categories
https://bugs.kde.org/show_bug.cgi?id=421288 Bug ID: 421288 Summary: Unable to delete some categories Product: kmymoney Version: 5.0.8 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-devel@kde.org Reporter: mfcarp...@gmail.com Target Milestone: --- SUMMARY I have some categories that I can't delete when I right click on the category the Delete category is greyed out. These categories are only in expenses and there is only approximately 12 of them that have the Delete category greyed out. Some of these categories I wish to delete have no transactions and some have transactions so it appears to make no difference. Of my other categories that have transactions and I don't want to delete I can delete those should I choose to. OBSERVED RESULT Can't delete category for some expenses EXPECTED RESULT Ability to delete any category SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 20.04 Kernel 5.4.0-29-generic ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
Re: Question about Future cashflow
Hi Juan, On Samstag, 9. Mai 2020 23:56:33 CEST Juan Pablo Toro wrote: > Hi guys. There may be women here also :) > I am new to Kmymoney. I have been using Quicken for ever but I had > it. I downloaded Kmymoney and so far so good. Quick question about the > forecast feature. how can I get a graph showing the future cashflow of my > accounts? You can do that by using the Forecast view. If you don't see it, you may have to enable the plugin before it shows up in the plugin configuration of KMyMoney. Details about the functionality can be found in the KMyMoney manual at https://docs.kde.org/stable5/en/extragear-office/kmymoney/details.forecast.html Also, the reporting section contains reports for forecasts. Check https://docs.kde.org/stable5/en/extragear-office/kmymoney/details.reports.html Hope that helps. If you have more questions, ask here or on IRC as last time. Cheers Thomas -- Regards Thomas Baumgart https://www.signal.org/ Signal, the better WhatsApp - Dear inventor of German: You forgot to define a translation for 'resize' (as verb). Please fix. -- Sebas Kügler - signature.asc Description: This is a digitally signed message part.
Fwd: Migration to Gitlab -- Update
Dear KMyMoney-Developer readers,
not all of you reading this list are active KMyMoney developers. Nevertheless,
I want to spread the word about the below information about the upcoming move
to a Gitlab based infrastructure provided by KDE sysadmin.
Since this will affect the way we access the code repository you all need to
know about that move. Well, at least those of you who build from the source
code out of the repo.
A word of caution: some of our procedures will change in the future and some
will stay as they are. Those that stay are easy to handle: business as usual.
To the ones that change we will have to get used to in the upcoming weeks and
months. This will certainly be a bit tricky and a rough ride here and there
in the beginning since I am by far not a Gitlab expert. I would rather say,
I start to learn the features and how to use it right now. So if one of you
is experienced in Gitlab usage, please let me know so I can contact you in
case of questions.
So much for today. As more details are made available by sysadmin I will
forward that to this list as well.
Stay safe and healthy and have a nice remaining weekend
Thomas
-- Forwarded Message --
Subject: Migration to Gitlab -- Update
Date: Sonntag, 10. Mai 2020, 09:48:50 CEST
From: Ben Cooksley
To: kde-core-devel , kde-devel
CC: sysadmin
Good morning all,
We recently had a rather lengthy discussion concerning the final
manner in which Gitlab will be deployed for KDE.
To ensure everything is clear, we'd like to summarise that and present
the final structure which has been agreed upon, along with details on
tools that will be able to assist Developers with the migration and
working with Gitlab in the long term.
-- Timeline --
At the moment we are intending to perform a bulk migration of all
repositories from git.kde.org to invent.kde.org on 16 May 2020.
When this transition commences, git.kde.org will be made read-only.
Following this, the current system will be kept active in a read-only
configuration for two weeks (until 30 May 2020) to allow for everyone
to smoothly transition local clones and any automated systems over to
the new Gitlab setup.
-- Structure --
Following lengthy discussion in the original thread, it was agreed
that the original sysadmin proposal of various categories would be
implemented, with repositories organised according to that structure.
You can find this documented at
https://cgit.kde.org/sysadmin/repo-metadata.git/tree/projects-invent?h=bshah/invent
-- Tooling --
To assist developers with the transition process, Sysadmin has
developed a utility ('git kpull') which once setup on a developers
system will automatically migrate any git.kde.org/anongit.kde.org to
the new structure automatically, before proceeding with a regular 'git
pull' when run in a Git repository.
Additionally, as some developers had concerns regarding locating
repositories, an additional utility known as 'git kclone' is being
shipped as well. This will allow developers to run "git kclone
" to clone a repository.
In the majority (95%) of cases we expect "" to be
identical to the repository name (frameworks/kcoreaddons being
kcoreaddons for instance), however where the name is common (such as
'dialer') then it will be prefixed by the name of the originating
project (so maui/dialer would have an identifier of maui-dialer)
following the convention we use at the moment for projects wishing to
have a repository using a common name.
It should be noted that 'git kclone' is also able to perform bulk
clones based on wildcard patterns (which you could use to clone all
frameworks by running "git kclone frameworks/*" for example)
Instructions on how to set this up on your system will be sent out
closer to the migration commencing.
-- Continuous Integration --
Following the migration, we will continue to use our existing Jenkins
based setup. Migration to using Gitlab for CI purposes will take place
at a later date once the necessary adjustments to the CI
infrastructure have been completed.
During the intervening time CI capability will be available on Gitlab
for evaluation and testing purposes only.
This is not supported as a standard production level service by
Sysadmin and therefore should not be relied upon by projects as part
of their workflow.
-- Tasks --
Tasks will be migrated from Phabricator at a future point in time.
These will remain on Phabricator for the time being and are not
affected by the migration.
Projects wishing to start entirely new boards and not needing to work
with existing boards on Phabricator should feel free to begin making
use of their new Gitlab boards following the migration.
-- Migration from Phabricator --
Existing code reviews will not be migrated from Phabricator as part of
this migration process and will need to be completed using the usual
process on Phabricator. It is expected that following the completion
of the migration of code hosting that no further new reviews will be
