Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
ID | ||||||||||||
0034456 | ||||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
feature request | [Retail Modules] Web POS | minor | always | 2016-11-09 17:53 | 2016-11-09 17:53 | |||||||
Reporter | malsasua | View Status | public | |||||||||
Assigned To | Retail | |||||||||||
Priority | normal | Resolution | open | Fixed in Version | ||||||||
Status | new | Fix in branch | Fixed in SCM revision | |||||||||
Projection | none | ETA | none | Target Version | ||||||||
OS | Any | Database | Any | Java version | ||||||||
OS Version | Database version | Ant version | ||||||||||
Product Version | SCM revision | |||||||||||
Review Assigned To | ||||||||||||
Regression level | ||||||||||||
Regression date | ||||||||||||
Regression introduced in release | ||||||||||||
Regression introduced by commit | ||||||||||||
Triggers an Emergency Pack | No | |||||||||||
Summary | 0034456: the manifest date should be stored in backend | |||||||||||
Description | in some circumstances, to know what is the date of the manifest in the terminals is very useful. So, we can to know if this terminal has loaded the last manifest generated in backend. It could be stored in the log client | |||||||||||
Steps To Reproduce | n/a | |||||||||||
Tags | No tags attached. | |||||||||||
Attached Files | ||||||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |
Issue History | |||
Date Modified | Username | Field | Change |
2016-11-09 17:53 | malsasua | New Issue | |
2016-11-09 17:53 | malsasua | Assigned To | => Retail |
2016-11-09 17:53 | malsasua | Triggers an Emergency Pack | => No |
Copyright © 2000 - 2009 MantisBT Group |