For those interested in this feature, it's good to hear feedback and
interest.
For general feedback or support, I think the original "bug" (enhancement)
report is probably best so there is a track record of it.
https://bugs.gnucash.org/show_bug.cgi?id=113772
For specific feedback about what is currently being implemented, there is
also the option to reply/comment on the various conversations in the Push
Request (jargon for the discussion where the code change is being
proposed). https://github.com/Gnucash/gnucash/pull/1623
<https://github.com/Gnucash/gnucash/pull/1623#issuecomment-1530788858>
It's an evolving conversation that requires consensus at some point, on
smaller and bigger issues, with respect for contradicting opinions and the
effort, needs and experience of core developers in terms of UI and coding
standards as well as maintenance and user support considerations. At a
minimum, this first simple (and limited) implementation will be offered in
one form or another, even if it takes the form of a custom report to start
(custom reports are user defined, so anybody can add one to their own
installation based on a provided template, but they are not part of the
official release or maintenance, hence not guaranteed to be maintained).
That's because until users can try it, I think it can be hard to provide
feedback. Some guidance will be provided on how to install it as a custom
report if we go that route first, but this is still being discussed. It
will be important for users to understand the limitations of this first
implementation, so we will need to work on some wiki documentation as well.
Whether it leads to a fuller implementation of analytical accounting
features to gnucash will come down to user interest and participation in
doing the actual work (not all of it is coding, a lot of it is developing
and commenting on functional requirements, writing documentation, answering
user questions, etc).
Sincerely,
Vincent Dawans
On Thu, May 4, 2023 at 9:59 AM NoobAlice wrote:
> Seconded! This would be a massive improvement to the excellent GnuCash,
> in my opinion. Thank you so much, Vincent! As described, this feature
> would add so much more utility in so many areas of reporting.
>
> Besides flywire's "classification/category/dimension," I would also add
> "jobs/projects" as keywords for anyone hunting down this thread later.
>
> > Message: 8 Date: Tue, 2 May 2023 19:26:46 +1000 From: flywire > <
> flywi...@gmail.com> To: Vincent Dawans Cc:
> Gnucash > Users Subject: [GNC] Tags for >
> classification/category/dimension transaction report Message-ID: >
> >
> Content-Type: text/plain; charset="UTF-8" Re: >
> https://lists.gnucash.org/pipermail/gnucash-user/2023-May/106749.html >
> Vince you are a champion! >
> https://github.com/Gnucash/gnucash/pull/1623#issuecomment-1530788858 >>
> My personal view is this workaround is the most significant improvement
> > since V2.
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
>
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
