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 701211 - Register2 version General Ledger is foreshortened
Register2 version General Ledger is foreshortened
Status: RESOLVED OBSOLETE
Product: GnuCash
Classification: Other
Component: Regist-2
2.5.x
Other Windows
: Normal normal
: future
Assigned To: gnucash-ui-maint
gnucash-ui-maint
Depends on:
Blocks:
 
 
Reported: 2013-05-29 17:43 UTC by David Carlson
Modified: 2018-06-29 23:16 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description David Carlson 2013-05-29 17:43:06 UTC
After opening a large file with Release 2.5.2 in Windows 7 64 bit, and clicking through the 3 entry point not found warnings and cancelling the since last run assistant:

I click Tools: General ledger.  Only transactions after 4-29-2013 appear (for this particular file).  There seems to be no way to see earlier transactions.
Comment 1 David Carlson 2013-05-29 17:47:05 UTC
the old style general ledger has the same limitation.
Comment 2 David Carlson 2013-05-29 17:48:38 UTC
For some reason I have to log in again for each new commit, regardless of how quickly I move.
Comment 3 David Carlson 2013-05-29 17:49:41 UTC
that time (less than 4 minutes) I was still logged in.
Comment 4 Geert Janssens 2013-05-30 14:11:00 UTC
David, I'm afraid I don't understand what comment 3 and comment 4 are talking about. GnuCash doesn't have a login mechanism ?

Regarding the General Ledger issue: are you sure this is different from GnuCash 2.4.x ?

I remember I refused to apply a patch recently that proposed to change the time span for which to show transactions in the GL from 1 month to 1 year (bug 689092).

I'm not against increasing this, but I wanted a more general solution than that patch. More discussion on that subject, please do so on bug 689092.
Comment 5 David Carlson 2013-05-30 19:15:38 UTC
Taking your comments in order:  

I was being kicked out of bugzilla and I needed to log back into bugzilla several times to complete my report.  I do not know why, unless the IP addresses of some Tor exit nodes are banned, G-lined or whatever.

Regarding GL: does it default to show only 1 month previous to the end of the file?   I also only saw a month of transactions using 2.4.13, but it appeared that it could be changed to filter whatever range I wanted.  If so I stand by my last comment in the developer maillist that filtering should be flagged in the tab, etc.

I think that I might add those comments to bug 689092.
Comment 6 Geert Janssens 2013-05-31 11:40:30 UTC
I checked and indeed the old GL allowed to change the filter, while the new GL doesn't.

So I think this is a regression that should be fixed.
Comment 7 Bob 2013-06-06 14:01:36 UTC
This is not quite accurate, the option to save was there but it did not do any thing so I greyed out the button for the GL. The reason for this is the filter values along with the old sort values were save as KVP data against the account displayed and as the GL does not have an account it did not save.

The new sort options are save in gconf against the account guid used for the register and so I created a dummy guid for the GL so I could save the same details for this register too.

At some point the filter options should probably be saved in the same way using gconf but I did not consider it important enough to spend time on it.

Oh, there was a problem with the filters on the GL, basically you ended up with just the blank transaction which I have fixed locally if that is what you are referring too.
Comment 8 John Ralls 2018-06-29 23:16:37 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=701211. Please continue processing the bug there and please update any external references or bookmarks.