David Valicek
My feedback
4 results found
-
4 votesDavid Valicek
shared this idea
·
-
576 votesDavid Valicek
supported this idea
·
An error occurred while saving the comment -
99 votesDavid Valicek
shared this idea
·
-
308 votes
Concurrent multi-user support has been part of our long-term goals for a while now:
http://wiki.gnucash.org/wiki/Roadmap#Database_and_QOFTime to update the status of this feature request…
Note it still says “long-term”, which currently means several years ahead of us.David Valicek
supported this idea
·
Yes, custom classification/tagging/labeling of transactions as well as classification/tagging/labeling of invoices, jobs, etc is a really important feature.
This classification should ideally enable a hirerarchy, as Ben Bucksch in his post to the original feature request wrote. This enables to analyse/report expenses per Program>Project>ProjectTeam or per a hierarchy of cost centres or per a hierarchy of customers or whatever else like this.
Enable putting the transaction into zero, one or more such a custom classes.
Please let me distinguish such a "transaction classification" feature as special case of "user defined fields/attributes" which I describe in a separate request:
http://gnucash.uservoice.com/forums/101223-feature-request/suggestions/1951947-user-defined-fields-attributes?ref=title