Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0021938Openbravo ERP09. Financial managementpublic2012-10-15 13:432013-01-22 10:33
ReporterVictorVillar 
Assigned ToioritzCia 
PriorityurgentSeverityminorReproducibilityalways
StatusnewResolutionopen 
PlatformOS5OS Version
Product Versionpi 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerOBPS
Web browser
ModulesCore
Support ticket17434
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0021938: Payment date should be mandatory
DescriptionPayment date should be mandatory in all the places where it is possible fill it.
Steps To ReproduceAs group admin role,
Go to Payment In or Payment out window and realise that it is a no mandatory field.

Also in Purchase invoice window and in Sales invoice window, the Add Payment pop-up should warn to the user in case the date introduced a wrong date.
Proposed SolutionIt should be a mandatory field and review the rest of the windows where they are used
Additional Information
TagsNo tags attached.
Relationships
related to defect 0022576 closed iciordia Issue 21938: try-api fails. 
related to defect 00219403.0MP20 closed jecharri If there is a register without payment date the payment report shows NPE error 
Attached Files? 21938.export (47,101) 2013-01-16 11:15
https://issues.openbravo.com/file_download.php?file_id=5895&type=bug
diff 21938apiChange.diff (1,551) 2013-01-16 11:15
https://issues.openbravo.com/file_download.php?file_id=5896&type=bug
Issue History
Date ModifiedUsernameFieldChange
2012-10-15 13:43VictorVillarNew Issue
2012-10-15 13:43VictorVillarAssigned To => dmiguelez
2012-10-15 13:43VictorVillarModules => Core
2012-10-15 13:43VictorVillarOBNetwork customer => Yes
2012-10-15 13:43VictorVillarSupport ticket => 17434
2012-10-15 13:43VictorVillarResolution time => 1352847600
2012-10-15 15:58VictorVillarRelationship addedrelated to 0021940
2012-10-15 16:16dmiguelezAssigned Todmiguelez => jonalegriaesarte
2012-10-20 08:45jonalegriaesarteAssigned Tojonalegriaesarte => ioritzCia
2012-11-02 14:52ioritzCiaTarget Version3.0MP17 => 3.0MP18
2012-12-04 09:12jonalegriaesarteSeveritymajor => minor
2012-12-04 11:51jonalegriaesarteTarget Version3.0MP18 => 3.0MP19
2012-12-14 09:49ioritzCiaNote Added: 0054929
2013-01-09 11:27jonalegriaesarteTriggers an Emergency Pack => No
2013-01-09 11:27jonalegriaesarteTarget Version3.0MP19 => 3.0MP20
2013-01-16 11:00jonalegriaesarteNote Added: 0055535
2013-01-16 11:00jonalegriaesarteTypedefect => design defect
2013-01-16 11:15ioritzCiaFile Added: 21938.export
2013-01-16 11:15ioritzCiaFile Added: 21938apiChange.diff
2013-01-16 11:16ioritzCiaRelationship addedrelated to 0022576
2013-01-22 09:33VictorVillarIssue Monitored: networkb
2013-01-22 10:33jonalegriaesarteTarget Version3.0MP20 =>

Notes
(0054929)
ioritzCia   
2012-12-14 09:49   
Test Plan:

- The testing of the issue itself is really simple. No it does not allow to have a null payment date, so, try to insert one.
- A buildvalidation has been implemented. To test it works correctly, set the payment date of any payment to null and try to update the instance. An error will arise while executing update.database. The user can enter the application and will see an alert pointing to every payment that does not have payment date and requesting to set to it a date. Once every payment is fixed the instance can be updated again.
(0055535)
jonalegriaesarte   
2013-01-16 11:00   
Clasified as design defect. The patch is ready, but we need to evaluate the risk