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 577965 - Feature "save report" is hidden, unclickable and not documented
Feature "save report" is hidden, unclickable and not documented
Status: RESOLVED INCOMPLETE
Product: GnuCash
Classification: Other
Component: Reports
git-master
Other All
: Normal enhancement
: ---
Assigned To: Andreas Köhler
Andreas Köhler
Depends on:
Blocks:
 
 
Reported: 2009-04-04 21:44 UTC by Øyvind Jensen
Modified: 2018-06-29 22:20 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Øyvind Jensen 2009-04-04 21:44:27 UTC
A nice improvement for reports would be if the options were stored and used automatically the next time you generate the report.  

This provides convenience, and would be a simpler solution than the one suggested in bug#571208.  But I also believe that it would resolve lots of other issues that currently populate the bugtracker:

a) Reports from huge transaction lists take a long time.  If the default options need to be changed, that time is wasted.  ( bug#107282 )  By applying the options from last time, there is better chance that the report is what is wanted.

b) Closing a heavily customized report by accident leads to the frustration reported in bug#516611      

c) It appears that many users keep lots of pages open in order to avoid reconfiguring the reports every time.  If users are constantly filling the gnucash window with lots of dormant report tabs, the user interface gets unnecessary cluttered.  (no bug opened on that though...)

d) Lots of open report tabs lead to long startup times ( bug#116565 ).
Comment 1 C.Ernst 2009-04-16 21:22:12 UTC
Not sure if I understand you correctly, but you already can save, close and reopen reports: 
http://wiki.gnucash.org/wiki/FAQ#Q:_How_do_I_save_the_options_I_have_set_on_a_built-in_report_as_a_custom_report.3F
Does this solve your problem and that of bug#571208?
Comment 2 Øyvind Jensen 2009-04-27 09:17:16 UTC
Actually it does solve my problem, I just couldn't figure out how to use this feature.

As a feature request, this bug report appear to be solved.  However, from a usability point of view, I think it is still relevant.  The feature is too important to be hidden away in the user interface.

I have two suggestions:

1.) "Add report" button should always be clickable, the name of the report could be entered in a dialog box.

- Since the "Add report" button is deactivated until you rename the report, users are less likely to give it any attention.  

- Even if you happen to notice the button, it is not clear how it can be activated.


2.) The otherwise excellent tutorial and concept guide does not explain how to save reports.  (At least it is not easy to find an explanation.)  Isn't the feature important enough to go into the tutorial?

Comment 3 Øyvind Jensen 2009-04-27 09:39:13 UTC
Changed bug title to reflect previous comment
Comment 4 Steven N. Severinghaus 2010-01-04 18:52:31 UTC
Another possibility:

* Rename the "Add report" button to "Save report".
* Saving a built-in report automatically results in a custom report with whatever parameters (including name) that were selected at the time.
* Saving a custom report simply saves it, replacing whatever the report was when it was opened.

This might be more intuitive, more like the file-open-save idiom.
Comment 5 Christian Stimming 2010-12-31 11:32:30 UTC
Is this still an issue with 2.4.0?
Comment 6 Christian Stimming 2011-01-17 09:10:29 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 7 John Ralls 2018-06-29 22:20:20 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=577965. Please update any external references or bookmarks.