[l10n_nl] duplicates standard account types, but without report type

Bug #919932 reported by Stefan Rijnhart (Opener)
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Fix Released
Low
OpenERP R&D Addons Team 3

Bug Description

Hi,

the chart of accounts in l10n_nl duplicates the standard OpenERP account types, but without the report type parameter. The chart of accounts should use the standard OpenERP account types instead.

Cheers,
Stefan.

Related branches

Revision history for this message
Ravish(OpenERP) (rmu-openerp) wrote :

Hello Stefan Rijnhart,

I have checked your both issues at my end.

#issue1 : The chart of accounts in l10n_nl duplicates the standard OpenERP account types, but without the report type parameter

#issue2: The chart of accounts should use the standard OpenERP account types instead.

But,I have conformed both the issues differently . #issue 2 is set as wishlist for future road map.
Hope you understand us.

Thanks!

Changed in openobject-addons:
status: New → Confirmed
importance: Undecided → Low
assignee: nobody → OpenERP R&D Addons Team 3 (openerp-dev-addons3)
Revision history for this message
Stefan Rijnhart (Opener) (stefan-opener) wrote :

Hi Ravish,

thank you for your response.

I agree that you could distinguish the two separate issues if you want to. However, I disagree with the status 'wishlist for future roadmap' for using the account types defined in the account module.

Correct me if I am wrong, but I see this as an undocumented API change on your side. In earlier releases of OpenERP, these account types were not present and had to be defined by every localisation module for its own use. The fact that these account types are now available globally is a very good thing, but we need to get the opportunity to adapt the localisation modules to this change. The future road map is too late. If users or developers install a localisation module and want to check their configuration, they are confronted with a duplicated set of account types, of which they cannot see which are used and which are not.

Please tell me, if right after the release candidate is not a good time to update the localisation modules to undocumented changes in the API, then what is? If you want to streamline the process for the new release then go ahead and document your changes, freeze the API way ahead of the release candidate and let us know so that we can adapt in an earlier stage. You would do everyone a favour.

Cheers,
Stefan.

Revision history for this message
Meera Trambadia (OpenERP) (mtr-openerp) wrote :

Hello Stefan,

We agree with you.We are surely going to review/merge your branch to get the correct fix for 6.1.

Just like to bring into notice here that .pot and .po files also needs to be reviewed.

Thanks for reporting and contributing a fix for the bug.

Thanks,
Meera

Changed in openobject-addons:
status: Confirmed → Fix Committed
Changed in openobject-addons:
milestone: none → 6.1
Revision history for this message
qdp (OpenERP) (qdp) wrote :

merged in revision 6606
revision-id: <email address hidden>

Thanks for the contribution, Stefan

Changed in openobject-addons:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.