Openbravo Issue Tracking System - Openbravo Deployment Options | ||||||||||||
View Issue Details | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | |||||||
0007119 | Openbravo Deployment Options | Appliance rPath | public | 2009-01-23 19:36 | 2009-08-31 16:23 | |||||||
Reporter | psarobe | |||||||||||
Assigned To | jpabloae | |||||||||||
Priority | normal | Severity | major | Reproducibility | sometimes | |||||||
Status | closed | Resolution | duplicate | |||||||||
Platform | OS | 5 | OS Version | |||||||||
Product Version | 2.40 | |||||||||||
Target Version | Fixed in Version | |||||||||||
Merge Request Status | ||||||||||||
Review Assigned To | ||||||||||||
Support ticket | ||||||||||||
OBNetwork customer | No | |||||||||||
Summary | 0007119: When applying an update, the console lost the session | |||||||||||
Description | When you are applying a MP, for instance 240MP0->240MP1, if for some how it takes too much time (I cannot explain the meaning of "too much time") the console lost the session and the screen is not refreshed so the user thinks that the process is still running when not. The consequences are: 1. The user can wait for ever 2. If you are sick of waiting and click in other menu option, the console gets logout. This can bother the user 3. The user doesn't know if the update finished successfully or not As and end user that has experimented this behavior I can say it's very annoying | |||||||||||
Steps To Reproduce | ||||||||||||
Proposed Solution | The console should be refreshed | |||||||||||
Additional Information | ||||||||||||
Tags | No tags attached. | |||||||||||
Relationships |
| |||||||||||
Attached Files | ||||||||||||
Issue History | ||||||||||||
Date Modified | Username | Field | Change | |||||||||
2009-01-23 19:36 | psarobe | New Issue | ||||||||||
2009-01-23 19:36 | psarobe | Assigned To | => jpabloae | |||||||||
2009-01-23 19:36 | psarobe | OBNetwork customer | => No | |||||||||
2009-01-28 10:29 | jpabloae | Status | new => acknowledged | |||||||||
2009-06-19 06:04 | jpabloae | Status | acknowledged => scheduled | |||||||||
2009-06-19 06:04 | jpabloae | fix_in_branch | => pi | |||||||||
2009-06-19 06:04 | jpabloae | Relationship added | duplicate of 0007220 | |||||||||
2009-06-19 06:04 | jpabloae | Status | scheduled => closed | |||||||||
2009-06-19 06:04 | jpabloae | Note Added: 0017443 | ||||||||||
2009-06-19 06:04 | jpabloae | Duplicate ID | 0 => 7220 | |||||||||
2009-06-19 06:04 | jpabloae | Resolution | open => duplicate | |||||||||
2012-07-19 13:11 | gorka_gil | Category | Appliance stack => Appliance rPath |
Notes | |||||
|
|||||
|
|