Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0019114 | Openbravo ERP | 03. Procurement management | public | 2011-11-21 09:14 | 2011-12-13 16:43 |
|
Reporter | jonalegriaesarte | |
Assigned To | mtaal | |
Priority | urgent | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | |
Platform | | OS | 5 | OS Version | |
Product Version | pi | |
Target Version | 3.0MP7 | Fixed in Version | 3.0MP7 | |
Merge Request Status | |
Review Assigned To | |
OBNetwork customer | |
Web browser | |
Modules | Core |
Support ticket | |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0019114: Amounts not formatted properly in grid view |
Description | Amounts not formatted properly in grid view. They do not follow the format defined in Format.xml |
Steps To Reproduce | - login
- go to Purchase Order screen and view it in grid mode
- see that the Total Gross Amount is NOT formatted using two fixed decimals as defined in Format.xml, 224.2 should be shown as 224.20
- if you edit (inline or in full edit) the amounts display correctly |
Proposed Solution | |
Additional Information | |
Tags | Regression |
Relationships | related to | defect | 0017531 | 3.0MP4 | closed | mtaal | Description field with 2 rows looks nasty in grid view | has duplicate | defect | 0019245 | 3.0MP7 | closed | mtaal | Re-introduce 1000 separators | related to | defect | 0018992 | | closed | alostale | Monetary amounts are not properly formatted in grid view |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2011-11-21 09:14 | jonalegriaesarte | New Issue | |
2011-11-21 09:14 | jonalegriaesarte | Assigned To | => alostale |
2011-11-21 09:14 | jonalegriaesarte | Modules | => Core |
2011-11-21 09:16 | jonalegriaesarte | Severity | major => minor |
2011-11-21 09:16 | jonalegriaesarte | Target Version | 3.0MP6 => 3.0MP7 |
2011-11-23 08:59 | alostale | Relationship added | related to 0018992 |
2011-11-23 09:01 | alostale | Status | new => scheduled |
2011-11-23 09:01 | alostale | fix_in_branch | => pi |
2011-12-01 12:01 | alostale | Relationship added | related to 0017531 |
2011-12-01 13:36 | alostale | Note Added: 0043651 | |
2011-12-12 09:57 | mtaal | Assigned To | alostale => mtaal |
2011-12-12 11:23 | hgbot | Checkin | |
2011-12-12 11:23 | hgbot | Note Added: 0043787 | |
2011-12-12 11:23 | hgbot | Status | scheduled => resolved |
2011-12-12 11:23 | hgbot | Resolution | open => fixed |
2011-12-12 11:23 | hgbot | Fixed in SCM revision | => http://code.openbravo.com/erp/devel/pi/rev/18cf176c087fef14aa0e9475a24af739f7b77c63 [^] |
2011-12-12 11:24 | mtaal | Relationship added | has duplicate 0019245 |
2011-12-12 12:11 | alostale | Note Added: 0043796 | |
2011-12-12 12:11 | alostale | Status | resolved => closed |
2011-12-12 12:11 | alostale | Fixed in Version | => 3.0MP7 |
2011-12-12 12:11 | alostale | Tag Attached: Regression | |
2011-12-13 16:43 | hudsonbot | Checkin | |
2011-12-13 16:43 | hudsonbot | Note Added: 0043841 | |
Notes |
|
|
Fix for 0017531 adds formatCellValue method to OBViewGrid. The problem is this methods returns the value without formatting it in case it is not a String with \n.
Completely removing this method solved this issue though 0017531 appears again. Returning super formatCellValue does not work... |
|
|
(0043787)
|
hgbot
|
2011-12-12 11:23
|
|
Repository: erp/devel/pi
Changeset: 18cf176c087fef14aa0e9475a24af739f7b77c63
Author: Martin Taal <martin.taal <at> openbravo.com>
Date: Mon Dec 12 11:22:51 2011 +0100
URL: http://code.openbravo.com/erp/devel/pi/rev/18cf176c087fef14aa0e9475a24af739f7b77c63 [^]
Fixes issue 19114: Amounts not formatted properly in grid view
---
M modules/org.openbravo.client.application/web/org.openbravo.client.application/js/grid/ob-view-grid.js
---
|
|
|
|
Tested pi@45ff7d718f06
Code review.
Verified it fixes the reported issue.
Verified 0017531 is still fixed.
No other regression possibility figured out. |
|
|
|
|