GNOME Bugzilla – Bug 535424
"Since Last Run Druid" docs out of sync with 2.2 UI
Last modified: 2018-06-29 22:04:58 UTC
Please describe the problem: When the since last run druid is run, it shows only the scheduled transactions with reminders if set. There is no forward or back button, so no way to navigate to the other pages that are quoted in the help files. Possibly tied in to this, the present and future totals at the bottom of account pages are always the same. Steps to reproduce: 1. Start the since last run druid 2. 3. Actual results: A page opens showing a list of scheduled transactions with reminders, if any Expected results: Extra pages for the reminders and the automatically inserted bills Does this happen every time? yes Other information:
The Since Last Run dialog changed substantially in 2.2 … it's no longer a multi-page druid, but only a single-page tree of all instances of all types (already-created, reminders, to-create, &c.) of SXes. Are you sure you have other types of entries (auto-created, as you say) since you've last run the SX dialog?
OK, I have all types of entry showing on the one page, but there are no values showing for the entries. I would have thought that would be the monetary amount of the transaction. Please correct me if I'm wrong.
No, there are no values displayed in that tree view. Generally, there's single value to display for a transaction, but instead one for each split. Practically, though, most transactions will have two splits with the same value, which could be shown. But the Since Last Run dialog does not display values for the transactions. I'm changing this to a Documentation bug, since the docs are out of sync.
(In reply to comment #3) > No, there are no values displayed in that tree view. Generally, there's single > value to display for a transaction, but instead one for each split. "Generally, there's *not a* single value […]"
Created attachment 178649 [details] [review] Preliminary patch for bug 535424 I attach a patch that update the documentation for the Since Last Run assistant. The patch is not complete: I don't know exactly what "Ignored" and "Postponed" do. I also see from po file that there are two strings ("Never" and "Need Value") that comes from the file "dialog-sx-since-last-run.c". Do Someone knows what they mean? Finally can someone confirm that the "value" column displayed in the Since Last Run assistant is meant to be empty as I understand from previous comments?
Please keep in mind that I am a user and not a developer but here is what I understand on how the scheduled transactions are working. Ignored: If a SX is being displayed, either to be created or as a reminder, the user can set the status to 'Ignored' to skip this event. The SX will not be entered in the register and the next reminder for this SX will be the next occurrence. For instance, if you have a SX set up with a reminder to transfer $500 at the end of the month to your savings account but you bought yourself a computer this month and don't have the money for this month's transfer then you would set the status to 'Ignored'. Postponed: If a SX has been listed with a status 'To-create' but you want to hold it and not have it entered to your register yet then you would set it to 'Postponed'. (In the past I had problems with this status because it changed the dates of the SX so I stopped using it and reset the status to 'Reminder' instead.) Never: I've never seen this one. Need Value: This is not a status. This is the string that shows up for a SX that's been entered with a variable. The variable is then displayed with a place to enter the actual amount. The initial value for this amount is '(Need Value)'. Value column: I can't confirm that it's *meant* to be empty (it would actually be nice to have the amount of a two-split SX displayed here) but I can confirm that the column is empty except for transactions entered with a variable amount. The 'Need Value' placeholder is displayed in the value column and once the actual amount has been entered, the value column contains that value. I hope this helps. If necessary I could provide you with screen shots for the above scenarios.
Thank you very much for the detailed description! I've added it to the patch and commited it to trunk. Do I have to commit the patch also in the 2.2 docs branch?
(In reply to comment #7) > Thank you very much for the detailed description! I've added it to the patch > and commited it to trunk. Do I have to commit the patch also in the 2.2 docs > branch? Well, since you are more or less the most active documentation maintainer, I'd say this is your call. The last documentation release for 2.2 has been 6 months ago. A lot of the documentation improvements were back ported from trunk to the 2.2 branch. So perhaps a new 2.2 documentation release is a good idea ? In that case IMO the patch in this bug surely makes sense. After this release, we can decide if we wish to continue to work on the 2.2 documentation (considering the limited man power available) or call it the final release and focus on the 2.4 documentation only.
I'm back again to this bug, because backporting the patch to 2.2 will requires more changes than I thought. So I close this bug. With the next GC release, if it's ok, I would like to also release a newer version of documentation due to a lot of modifications and closed bug since the last release. I dont't know how to make a new release but I'm willing to learn but that's another topic...
Cristian, I have opened bug 652350 to discuss the documentation release process further. I know most of the steps involved in the process (I have done some releases in the past), but I'd like to come to a written down process so you could also act as a (documentation) release manager. I'll work on this as soon as time permits. In the meantime, if you have comments, suggestions or whatever, feel free to add them to bug 652350.
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=535424. Please update any external references or bookmarks.