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 709251 - Closer match for report menu items and report titles
Closer match for report menu items and report titles
Status: RESOLVED OBSOLETE
Product: GnuCash
Classification: Other
Component: Reports
2.5.x
Other All
: Normal enhancement
: ---
Assigned To: gnucash-reports-maint
gnucash-reports-maint
Depends on:
Blocks:
 
 
Reported: 2013-10-02 10:51 UTC by Geert Janssens
Modified: 2018-06-29 23:19 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Geert Janssens 2013-10-02 10:51:59 UTC
This is a follow-up on bug 334939 and bug 696492.

Following three reports all have the same "Transaction Report" as report title (listed are the menu names of the reports):
- General Journal
- General Ledger
- Transaction Report

For the Transaction Report, this name obviously makes sense. For the other two less so. The problem here is that using the exact same report title for three different reports makes it more difficult to know which menu item was used to create the report. Ideally each report should have a unique title, closely matching the menu item for the report.

The following reports user "Register Report" as title, which is confusing as no such report exists:
- Account Report
- Account Report - Single Transaction

A better title would be "Account Report". It could be debated that the second report needs some suffix to indicate it's only on transaction being displayed, but that makes the title rather long.
Comment 1 Christian Stimming 2013-10-02 19:38:25 UTC
Yes, each report should have a unique title. +1 from me.
Comment 2 John Ralls 2018-06-29 23:19:36 UTC
GnuCash bug tracking has moved to a new Bugzilla host. The new URL for this bug is https://bugs.gnucash.org/show_bug.cgi?id=709251. Please continue processing the bug there and please update any external references or bookmarks.