Wrong search field order in account.account tree view

Hello sraps (KN dati),

Its not at all a big deal.

OpenERP provides you a way to customize the look and feel as per your desire/need.

If you want code field to appear first before name field, you are free to change the form view of Account.account object from Administration/Customization/User Interface/Views. Search by Account.account.form; you will see
name field record appearing before code. Alter the sequence. Your purpose will be served.

The product has taken care of nearly all the functional needs. We have our own accounting expert team on Launchpad.

However, we will be honored to have your precious suggestions to improve the product. Feel free to post blueprints on Launchpad.

This is not a bug really.

Thanks.

There are bunch of such "Invalid bugs" in OpenERP, that one have to change for each setup again and again. I agree that this does not shrink functional features of the package, but it definitely takes your time, when you work on daily basis.

For example - I am not talking of normal order of credit and debit account fields on each form, that in OpenERP are placed in random order, in each place - differently. There are agreed order on them - it is known as a rule of thumb for any seasoned accountant.

I am sorry to say, but I have been starting to collect such problematic cases in OpenERP (that are assigned for solving by programmers, not accountancy experts), where nobody cares about international practice, but rather talk all and over for months how to solve elementary thing.

Guys open your eyes - it is a bug. Which speaks for the maturity level of system.

I agree with both.

I agree with sraps that code field should be first located on search form.
That's the usual way of most accountants to begin looking for an account.

I agree it's not a bug. A bug is a not functioning part of system. Something
that doesn't let you operate in a correct way. If you can operate normally
and it's only usability problem... even if you have got to make 50clicks
instead of one, it's not a bug.

It's a clear wishlist. Said that... there is things like this one, that
should be taken in account. Solution is not to say adapt view, do it
yourself. Even me could make such a change.

But improving this little changes increases product usability for everybody
and... most important...you are going same line with published "oficial"
version...

Thank you!!!

Ana

2010/2/9 sraps (KN dati) <email address hidden>

> There are bunch of such "Invalid bugs" in OpenERP, that one have to
> change for each setup again and again. I agree that this does not shrink
> functional features of the package, but it definitely takes your time,
> when you work on daily basis.
>
> For example - I am not talking of normal order of credit and debit
> account fields on each form, that in OpenERP are placed in random order,
> in each place - differently. There are agreed order on them - it is
> known as a rule of thumb for any seasoned accountant.
>
> I am sorry to say, but I have been starting to collect such problematic
> cases in OpenERP (that are assigned for solving by programmers, not
> accountancy experts), where nobody cares about international practice,
> but rather talk all and over for months how to solve elementary thing.
>
> Guys open your eyes - it is a bug. Which speaks for the maturity level
> of system.
>
> ** Changed in: openobject-addons
> Status: Invalid => New
>
> --
> Wrong search field order in account.account tree view
> https://bugs.launchpad.net/bugs/519218
> You received this bug notification because you are subscribed to
> OpenObject Addons.
>
> Status in OpenObject Addons Modules: New
>
> Bug description:
> Normally no accountant would search on account name by default. So it is
> absolutely needed to change search field order moving "Code" field as first
> search field.
>
> Note: It should not be treated as wishlist, because this substantially
> degrades software maturity perception for customer. No normal accounting
> module would have name field in front of code field.
>
>
>

--
Ana Juaristi Olalde
Consultor Freelance OpenERP
www.anajuaristi.com
www.openerpsite.com
www.avanzosc.com
677 93 42 59 - 943 85 06 25

I assume we are building software for the people. So if there is part that does not function like user expects to it should function, and it could be changed by simply changing order of some tags - it is a bug.

Moreover there is no other misbehavior accounting feature like bug reporting in launchpad. If this part would not be implemented at all, then we could consider this as wishlist or as blueprint, still this part is implemented, so any such thing should be considered as bug related to UI.

Is this so hard to change. After all, this does not make any changes to API at all, so do not be afraid, it would not break anything...

Best regards,
Kaspars

Sorry sraps.. but I always say to my users: "Software is not made as YOU
expected to be made but as a programmer thought you would like and need it"

you can't fix as a bug everything they expect to be like... Defining the
line between a bug and a wishlist sometimes could be confusing but bug is
error, wishlist is improvement. This is the line for me.

2010/2/10 sraps (KN dati) <email address hidden>

> I assume we are building software for the people. So if there is part
> that does not function like user expects to it should function, and it
> could be changed by simply changing order of some tags - it is a bug.
>
> Moreover there is no other misbehavior accounting feature like bug
> reporting in launchpad. If this part would not be implemented at all,
> then we could consider this as wishlist or as blueprint, still this part
> is implemented, so any such thing should be considered as bug related to
> UI.
>
> Is this so hard to change. After all, this does not make any changes to
> API at all, so do not be afraid, it would not break anything...
>
> Best regards,
> Kaspars
>
> --
> Wrong search field order in account.account tree view
> https://bugs.launchpad.net/bugs/519218
> You received this bug notification because you are subscribed to
> OpenObject Addons.
>
> Status in OpenObject Addons Modules: New
>
> Bug description:
> Normally no accountant would search on account name by default. So it is
> absolutely needed to change search field order moving "Code" field as first
> search field.
>
> Note: It should not be treated as wishlist, because this substantially
> degrades software maturity perception for customer. No normal accounting
> module would have name field in front of code field.
>
>
>

--
Ana Juaristi Olalde
Consultor Freelance OpenERP
www.anajuaristi.com
www.openerpsite.com
www.avanzosc.com
677 93 42 59 - 943 85 06 25

Hello Subscribers,

Let the current situation be as it is for stable one.

The suggestion has been taken into consideration for the next version and it has been committed to trunk by revision 2981 <email address hidden>.

The trunk version contains an improvement that you can define your own search panel for any list view.

Thanks.

Of course the line is thin and debatable. Still we are building software for people so user interface inconsistencies should be considered as bugs too. We must understand that such "small" (and there are lot of them) annoying things can influence decision...

Anyway, thank you all for interest and contribution!