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

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0021938
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Openbravo ERP] 09. Financial managementminoralways2012-10-15 13:432013-01-22 10:33
ReporterVictorVillarView Statuspublic 
Assigned ToioritzCia 
PriorityurgentResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionpiSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0021938: 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
TagsNo tags attached.
Attached Files? file icon 21938.export [^] (47,101 bytes) 2013-01-16 11:15
diff file icon 21938apiChange.diff [^] (1,551 bytes) 2013-01-16 11:15 [Show Content]

- Relationships [ Relation Graph ] [ Dependency Graph ]
related to defect 0022576 closediciordia Issue 21938: try-api fails. 
related to defect 00219403.0MP20 closedjecharri If there is a register without payment date the payment report shows NPE error 

-  Notes
(0054929)
ioritzCia (developer)
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 (reporter)
2013-01-16 11:00

 Clasified as design defect. The patch is ready, but we need to evaluate the risk

- Issue History
Date Modified Username Field Change
2012-10-15 13:43 VictorVillar New Issue
2012-10-15 13:43 VictorVillar Assigned To => dmiguelez
2012-10-15 13:43 VictorVillar Modules => Core
2012-10-15 13:43 VictorVillar Resolution time => 1352847600
2012-10-15 15:58 VictorVillar Relationship added related to 0021940
2012-10-15 16:16 dmiguelez Assigned To dmiguelez => jonalegriaesarte
2012-10-20 08:45 jonalegriaesarte Assigned To jonalegriaesarte => ioritzCia
2012-11-02 14:52 ioritzCia Target Version 3.0MP17 => 3.0MP18
2012-12-04 09:12 jonalegriaesarte Severity major => minor
2012-12-04 11:51 jonalegriaesarte Target Version 3.0MP18 => 3.0MP19
2012-12-14 09:49 ioritzCia Note Added: 0054929
2013-01-09 11:27 jonalegriaesarte Triggers an Emergency Pack => No
2013-01-09 11:27 jonalegriaesarte Target Version 3.0MP19 => 3.0MP20
2013-01-16 11:00 jonalegriaesarte Note Added: 0055535
2013-01-16 11:00 jonalegriaesarte Type defect => design defect
2013-01-16 11:15 ioritzCia File Added: 21938.export
2013-01-16 11:15 ioritzCia File Added: 21938apiChange.diff
2013-01-16 11:16 ioritzCia Relationship added related to 0022576
2013-01-22 09:33 VictorVillar Issue Monitored: networkb
2013-01-22 10:33 jonalegriaesarte Target Version 3.0MP20 =>

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker