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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0041896
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[Openbravo ERP] A. Platformminorhave not tried2019-09-26 18:172022-02-01 08:07
ReporterALopeteguiView Statuspublic 
Assigned ToTriage Platform Base 
PrioritynormalResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0041896: Add new column in c_import_entry to know processing time

DescriptionCurrently in the table c_import_entry there are two columns related to processing time:
Created: Timestamp when import_entry is created.
Imported: Timestamp when import_entry is processed

It would be very valuable if we can know what is the processing time.
Steps To ReproduceCreate orders in the webpos, and check the c_import_entry table, you can find when the order was created in the c_import_entry, and when the order finished processing. But we can not know when it started to process and how long it took
Proposed SolutionOption A: Add new column in c_import_entry to save the timestamp when the entry started to process.

Option B: Add new column in c_import_entry to save the processing time in ms
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2019-09-26 18:17 ALopetegui New Issue
2019-09-26 18:17 ALopetegui Assigned To => platform
2019-09-26 18:17 ALopetegui Modules => Core
2019-09-26 18:17 ALopetegui Triggers an Emergency Pack => No
2022-02-01 08:07 alostale Assigned To platform => Triage Platform Base


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker