Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0012754 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| design defect | [Openbravo ERP] 09. Financial management | major | always | 2010-03-22 09:08 | 2012-04-24 15:52 | |||||||
| Reporter | manishkp | View Status | public | |||||||||
| Assigned To | naiaramartinez | |||||||||||
| Priority | high | Resolution | open | Fixed in Version | ||||||||
| Status | scheduled | Fix in branch | Fixed in SCM revision | |||||||||
| Projection | none | ETA | none | Target Version | ||||||||
| OS | Windows | Database | PostgreSQL | Java version | 1.6 | |||||||
| OS Version | XP | Database version | 8.3 | Ant version | 1.7 | |||||||
| Product Version | 2.50MP9 | SCM revision | ||||||||||
| Review Assigned To | ||||||||||||
| Web browser | ||||||||||||
| Modules | Core | |||||||||||
| Regression level | ||||||||||||
| Regression date | ||||||||||||
| Regression introduced in release | ||||||||||||
| Regression introduced by commit | ||||||||||||
| Triggers an Emergency Pack | No | |||||||||||
| Summary | 0012754: We Can Have Duplicate Tax Zone | |||||||||||
| Description | We Can Have Duplicate Tax Zone which is a bug. | |||||||||||
| Steps To Reproduce | Open ERP application -> Click Financial Management - > Accounting -> Setup -> Tax Rate form -> click new Tax Zone icon -> then add already available Tax Zone -> Click Save button | |||||||||||
| Tags | VMA-Reviewed | |||||||||||
| Attached Files | ||||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0047918) vmromanos (manager) 2012-04-24 15:52 |
It's currently possible to have duplicated tax zones for the same tax rate which is something wrong that should be fixed. However, the impact from a functional perspective is null, because the system only takes into account the first occurrence found in this table, so it doesn't matter the number of times the same tax zone has been defined. The fix consists in creating a check constraint in a table, but this change could generate important problems when updating any instance that has already duplicated tax zones. That's why we have decided to move this issue to "design defect", that should be fixed in the next Openbravo major version. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2010-03-22 09:08 | manishkp | New Issue | |
| 2010-03-22 09:08 | manishkp | Assigned To | => dalsasua |
| 2010-03-28 18:22 | dalsasua | Status | new => acknowledged |
| 2011-07-20 18:18 | dalsasua | Assigned To | dalsasua => jonalegriaesarte |
| 2012-04-03 12:20 | jonalegriaesarte | Assigned To | jonalegriaesarte => vmromanos |
| 2012-04-10 15:11 | vmromanos | Tag Attached: VMA-Reviewed | |
| 2012-04-16 13:59 | naiaramartinez | Assigned To | vmromanos => naiaramartinez |
| 2012-04-16 14:00 | naiaramartinez | Status | acknowledged => scheduled |
| 2012-04-16 14:00 | naiaramartinez | fix_in_branch | => pi |
| 2012-04-24 15:52 | vmromanos | Note Added: 0047918 | |
| 2012-04-24 15:52 | vmromanos | Type | defect => design defect |
| 2012-04-24 15:52 | vmromanos | fix_in_branch | pi => |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |