Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0019002
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Openbravo ERP] 01. General setupmajoralways2011-11-07 01:202015-01-19 20:29
ReporterpjuvaraView Statuspublic 
Assigned Toplujan 
PrioritynormalResolutionfixedFixed in Version
StatusclosedFix in branchFixed in SCM revisionn.a.
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product Version3.0MP4.1SCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0019002: System is not fully working with date format MM-DD-YYYY

DescriptionBy executing a superficial test with date format MM-DD-YYYY, I could detect two major defects: 19000 and 19001.

Both issues are significant enough to make the system inoperable for a US customer.

More issues can be present in the system and a comprehensive review and test of the support of alternative date formats is needed.
Steps To ReproduceN/A
TagsAccountingDemo
Attached Files

- Relationships [ Relation Graph ] [ Dependency Graph ]
related to defect 0019331 closedmarvintm Format date dd/mm/yyyy fails in P&E in return from customer 
depends on defect 0019000 closedvmromanos Balance sheet and P&L report does not work when system configured with MM-DD-YYYY date format 
depends on defect 0019001 closedvmromanos Incorrect accounting date and period in GL Journal Header when system date format is MM-DD-YYYY 
depends on defect 0019455 closedmarvintm The process scheduling fails after some time if using a different date format 

-  Notes
(0073496)
plujan (manager)
2015-01-14 16:28

 After several iterations, we have now automated some basic flows using MM-DD-YYYY format and also we have included this, including the use of point and comma as decimal and thousands separators, into our regular QA cycles.

Due the generic nature of the issue, it is not possible to declare that the system is "fully working" on MM-DD-YYYY format, but we have minimised the risk of an issue on this topic enough to consider it working as expected.

If any other issue related to this functionality is found in the coming releases, it should be treated as a separate issue linked to this one as "related".

- Issue History
Date Modified Username Field Change
2011-11-07 01:20 pjuvara New Issue
2011-11-07 01:20 pjuvara Assigned To => jonalegriaesarte
2011-11-07 01:20 pjuvara Modules => Core
2011-11-07 01:20 pjuvara Relationship added depends on 0019000
2011-11-07 01:20 pjuvara Relationship added depends on 0019001
2011-11-07 01:21 pjuvara version => 3.0MP4.1
2011-11-07 01:43 pjuvara Tag Attached: AccountingDemo
2011-12-19 10:47 iciordia Assigned To jonalegriaesarte => marvintm
2011-12-19 12:56 psarobe Relationship added related to 0019331
2012-01-10 18:34 marvintm Relationship added depends on 0019455
2012-02-29 12:45 iciordia Assigned To marvintm => plujan
2012-02-29 12:45 iciordia Type defect => design defect
2012-12-12 17:26 ioritzCia Triggers an Emergency Pack => No
2012-12-12 17:26 ioritzCia Severity critical => major
2015-01-14 16:23 plujan Status new => scheduled
2015-01-14 16:23 plujan fix_in_branch => pi
2015-01-14 16:28 plujan Note Added: 0073496
2015-01-14 16:28 plujan Status scheduled => resolved
2015-01-14 16:28 plujan Fixed in Version => 3.0PR15Q4
2015-01-14 16:28 plujan Fixed in SCM revision => n/a
2015-01-14 16:28 plujan Resolution open => fixed
2015-01-14 16:32 plujan Fixed in SCM revision n/a => n.a.
2015-01-14 16:32 plujan fix_in_branch pi =>
2015-01-19 20:29 iciordia Status resolved => closed

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker