While the account hierarchy allows each transaction to be assigned to a different sub-accounts, it would be useful to have classifications which apply to transactions accross sub-accounts. e.g. assume the following accounts exists

Where's ctrl-z when you need it? There's several aspects to this. Naive undo would include being able to remove some typing or a paste operation you did to a field that you didn't intend. Sophisticated undo would let you reverse a transaction that you messed up without having to hunt for what account it's in now. Even more sophisticated might be multiple levels of both Undo and Redo, and a hint in the menu next to each about what would happen if you chose that option.

This is another simple time-saver that's probably been mentioned elsewhere but may be worth listing here for tracking purposes.

Where's ctrl-z when you need it? There's several aspects to this. Naive undo would include being able to remove some typing or a paste operation you did to a field that you didn't intend. Sophisticated undo would let you reverse a transaction that you messed up without having to hunt for what account it's in now. Even more sophisticated might be multiple levels of both Undo and Redo, and a hint in the menu next to each about what would happen if you chose that option.

This is another simple time-saver that's probably been mentioned elsewhere…

As I recall reading on the GnuCash mailing list(s), developers will not include support for currencies that do not meet ISO requirements. Therefore, to use the likes of Ithaca hours or bitcoins, users have to rather inappropriately treat them as stocks, virtually exchanging them for an official currency before conducting real transactions. Either that or users must rely on the XXX placeholder currency, which has its own limitations.

I propose that GnuCash include some functionality for users to define custom currencies that behave just like regular official ones. This functionality would allow for users to point GnuCash to where it can find exchange rates with other currencies or to manually specify them. It would also allow for users to peg the value of their custom currencies to officially recognized ones.

As I recall reading on the GnuCash mailing list(s), developers will not include support for currencies that do not meet ISO requirements. Therefore, to use the likes of Ithaca hours or bitcoins, users have to rather inappropriately treat them as stocks, virtually exchanging them for an official currency before conducting real transactions. Either that or users must rely on the XXX placeholder currency, which has its own limitations.

I propose that GnuCash include some functionality for users to define custom currencies that behave just like regular official ones. This functionality would allow for users to point…

I’m reopening this feature request because currently it’s not possible to attach items to an invoice. It’s only possible to attach items to regular transactions (not associated with invoices/bills).
This as a separate corresponding bugzilla item: https://bugzilla.gnome.org/show_bug.cgi?id=735408

Allow multiple users, in a business to access the database at the same time so that multiple transactions can be entered or updated simultaneously, and do so with remote access capabilites like Terminal Server (Windows) or X-Term sessions (Linux/Unix) .
This is a feature in many commercial programs and this is exactly why many business users of such programs are not using GnuCash.
If GnuCash wants to secure donations from the business community beyond the home or individual operating as a business, this feature will make GnuCash extremely attractive to a market that routinely pays $3,000 to $5,000 for products lke Quickbooks Pro with $850-$1,000 per year support contracts.

Allow multiple users, in a business to access the database at the same time so that multiple transactions can be entered or updated simultaneously, and do so with remote access capabilites like Terminal Server (Windows) or X-Term sessions (Linux/Unix) .
This is a feature in many commercial programs and this is exactly why many business users of such programs are not using GnuCash.
If GnuCash wants to secure donations from the business community beyond the home or individual operating as a business, this feature will make GnuCash extremely attractive to a market that routinely pays $3,000 to $5,000 for products…

Gnucash needs a robust cashflow forecast with graph, where one can select which accounts and show future cashflow for 30, 90, 180 and 360 days based on scheduled transactions (both credits and debits) that have not yet been entered. e.g. my pay comes every 2 weeks, I get some extra income in June and August that I can estimate, and I have some bills that are every month, others twice a year... I need to know when things will "pile up" requiring a transfer from higher yielding savings accounts into checking. Microsoft Money had a great forecast with a graph so one could identify to the day when balances would run low and plan ahead for transferring money from other accounts. The wiki wishlist for GnuCash has a very detailed explanation of how cash flow forecasting could work, also suggesting the ability to create estimated cashflow from past transactions (which Money could do), but for my part a starting place would be known scheduled transactions that haven't yet been entered. Being able to modify single occurrences of scheduled transactions would also be great without having to edit the entire series (e.g. most months my utility bills are X but I know the electricity bill is higher in the 3 months of summer so).

Gnucash needs a robust cashflow forecast with graph, where one can select which accounts and show future cashflow for 30, 90, 180 and 360 days based on scheduled transactions (both credits and debits) that have not yet been entered. e.g. my pay comes every 2 weeks, I get some extra income in June and August that I can estimate, and I have some bills that are every month, others twice a year... I need to know when things will "pile up" requiring a transfer from higher yielding savings accounts into checking. Microsoft Money had a great forecast with a graph…

One problem with Gnucash is that a user may accidentally change a transaction in a previous month or year. For example, it is possible to delete a transaction that should not be deleted. Also, if a user enters the wrong date in a new transaction (e.g. when typing the date, the year is wrongly entered) the transaction will enter the register in a previous period, but the user may not know where it went. Thus the accounts could be in error due to an accidentally deleted transaction or incorrectly entered transaction.

In my experience training people to use Gnucash in the non-profit sector this has frequently happened.

SUGGESTED SOLUTION:
Add a feature where the entries in a month may be locked and password protected. Thus, after the data-entry clerk enters all the transactions for a month into Gnucash, the finance manager locks all the transactions with a password unknown to the data-entry clerk.

The lock would not prevent reports from being generated or data from being viewed, it would only prevent data from being changed in the locked period.

If subsequently, transactions in a previous month need to changed, the finance manager's password will be needed to unlock that month.

Such a lock could prevent both accidental changes to the accounts in a previous period and intentional attempts to manipulate the accounts to the data entry clerk's personal advantage.

One problem with Gnucash is that a user may accidentally change a transaction in a previous month or year. For example, it is possible to delete a transaction that should not be deleted. Also, if a user enters the wrong date in a new transaction (e.g. when typing the date, the year is wrongly entered) the transaction will enter the register in a previous period, but the user may not know where it went. Thus the accounts could be in error due to an accidentally deleted transaction or incorrectly entered transaction.

The aim is not absolute security but would prevent casual access to the information held. (Windows ACLs go some way towards this but any administrator could view the information.)
If this would be better done by securing the files outside the application, could someone tell me how?

Currently the CSV (and other like QIF) import dialog is very strict and gives NO facility for MAPPING of accounts to CSV columns etc.
No info on whether to put last column in csv as expenses:Office_Expenses or only Office_Expenses? and then whether gnucash is configured to show
only last of account names or fully qualified names. I tried BOTH combinations, still gnucash Fails EVERYTIME to map accounts.
behaviour I saw was - it maps ALL the entries to one account ( like all csv rows to Office_Expenses !!!)

Then - in last import dialog, we get mapped (or imbalance) accounts which are always distorted
and then I have to keep double clicking EACH row !!! to map it to particular a/c.
I can't even tell gnucash to repeat same for other rows !!!

So first item would be to have

A. Proper and EASY dialogs in Import Wizards

B. It should also allow - while mapping - as debit or credit columns corresponding to accounts

C. Import should be able to read FIRST line of csv file as Column-Headers and use it in mapping

Currently the CSV (and other like QIF) import dialog is very strict and gives NO facility for MAPPING of accounts to CSV columns etc.
No info on whether to put last column in csv as expenses:Office_Expenses or only Office_Expenses? and then whether gnucash is configured to show
only last of account names or fully qualified names. I tried BOTH combinations, still gnucash Fails EVERYTIME to map accounts.
behaviour I saw was - it maps ALL the entries to one account ( like all csv rows to Office_Expenses !!!)

It would be nice to have the option to place Gnucash-generated backup files in
a designated folder. This configuration setting might best appear on the same
Preferences tab as the Delete Backup Files preference. The preference pane
could display:
- the active backup folder (defaulting to the data file location),
- a folder selection widget, and
- a Select button to implement the change

I'm using gnu cash since two months ago and find it very good and user friendly. My only big problem is I am Persian and you don't have our calendar in the program. The same problem could happened to the people the other nations and countries.

With a custom fields I could solve (or at least workaround) the following issues described in separate threads:
- transaction classification
- add the ability to attached scanned images to invoices
- point of sale
- link any transaction to "the other party"

And more:
- I could fill-in bank account number of the other party at bank account transactions - and can later search according the bank account
- make notes to the transactions (it's a good idea to make more extensive notes to complex transactions so as you could remember later what was going on)
- and more

With a custom fields I could solve (or at least workaround) the following issues described in separate threads:
- transaction classification
- add the ability to attached scanned images to invoices
- point of sale
- link any transaction to "the other party"

And more:
- I could fill-in bank account number of the other party at bank account transactions - and can later search according the bank account
- make notes to the transactions (it's a good idea to make…