After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 527726 - Saved reports don't notice new accounts
Saved reports don't notice new accounts
Status: RESOLVED FIXED
Product: GnuCash
Classification: Other
Component: Reports
2.2.x
Other All
: Normal minor
: ---
Assigned To: gnucash-reports-maint
gnucash-reports-maint
Depends on: 649284
Blocks:
 
 
Reported: 2008-04-12 15:24 UTC by Conor O'Neill
Modified: 2018-06-29 22:03 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Conor O'Neill 2008-04-12 15:24:21 UTC
Please describe the problem:
If you have a saved (custom) report, then you later add a new account, the saved report does not take the new account(s) into selection.


Steps to reproduce:
1. Create a report using asset accounts, and save it. Close this report
2. Add a new asset account
3. Open the custom report. The new account is not processed.
4. Go into the report options, add the new asset account, so see the correct report.



Actual results:
You must add the new asset account each time

Expected results:
There should be a way of saving the updated report, including the corrected list of accounts

Does this happen every time?
Yes

Other information:
You can work around this by re-saving the report under a new name, but this will slowly clutter up the list of reports with obsolete entries.
Comment 1 Ian K 2011-02-09 13:01:48 UTC
I agree it causes clutter to rename a report in order to save changes. If the option to 'add report' was available when a change (e.g. adding an account) was made, then if the saved report already existed it could be overwritten. It is inconvenient to have to give a new name to a report in order to be allowed to save it.
For example I have a report called "Expenses YTD". I then add an account to it, rename it to "Expenses YTD2", save it, then delete "Expenses YTD". If I change it again I then revert back to "Expenses YTD", deleting YTD2 etc.
Comment 2 Carsten Rinke 2013-04-24 13:32:10 UTC
Fully agreeing to the point that this is user unfriendly design and implementation, I'd still consider this bug rather an enhancement request.

My proposal:
Change the severity to ENH, but raise the priority to HIGH.
Comment 3 Geert Janssens 2013-07-06 15:50:02 UTC
The patches proposed in bug 649284 should alleviate this. Saved reports still won't notice new accounts, but it will allow to update the report and save it again without having to go through the hassle of changing the name, save, delete the old saved report, change name back,...
Comment 4 Geert Janssens 2013-12-08 15:28:12 UTC
Rereading the original request, I believe this bug is now fixed. It is no longer necessary to do the report-rename-to-save dance in the 2.5 series. So it will be much easier to update an existing saved report when a new account is added.
Comment 5 John Ralls 2018-06-29 22:03:25 UTC
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=527726. Please update any external references or bookmarks.