Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0009059Openbravo ERPA. Platformpublic2009-05-16 13:042011-03-29 12:52
Reporterkenzo 
Assigned Toiciordia 
PrioritynormalSeveritymajorReproducibilityN/A
StatusnewResolutionopen 
PlatformOS20OS VersionUbuntu 8.10
Product Version2.50MP1 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0009059: Have the ability to roll back a core update if the build process goes wrong
DescriptionIf I go from 2.50 to 2.50MP1 and use the .obx files for the upgrade, I should be able to roll back to 2.50.

Currently, if something goes wrong as an example one is unable to update the database, there is no way to roll back the core update to the previous state before update.
Steps To Reproduce
Proposed SolutionHave the core be packaged prior to any upgrade. Then if some thing goes wrong you would have a .obx file which can be run to put the application and database back to previous state.
Additional Information
TagsNo tags attached.
Relationships
related to feature request 0010938 acknowledged iciordia There is not a way to rollback an update when updating the core of the application 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-05-16 13:04kenzoNew Issue
2009-05-16 13:04kenzoAssigned To => rafaroda
2009-05-18 10:24shuehnerIssue Monitored: shuehner
2009-05-22 16:11rafarodaAssigned Torafaroda => pjuvara
2009-05-22 19:33pjuvaraAssigned Topjuvara => iciordia
2009-09-02 13:27rafarodaNote Added: 0019420
2009-10-16 12:03psarobeRelationship addedrelated to 0010938
2011-03-29 12:47dalsasuaNote Added: 0035314
2011-03-29 12:52dalsasuaSeveritycritical => major

Notes
(0019420)
rafaroda   
2009-09-02 13:27   
According to http://wiki.openbravo.com/wiki/Bug_Reporting_Guidelines#How_to_Choose_the_Right_Severity [^] feature requests should not have Severity Critical.

If there no reason why they are Critical please down their priority to Major:
    * New functionality that would significantly increase the user base of the product.
    * Usability improvements.

Thanks.
(0035314)
dalsasua   
2011-03-29 12:47   
Reduced the severity, according to our reporting guidelines[1], because a FR cannot be critical:
[1] http://wiki.openbravo.com/wiki/Bug_Reporting_Guidelines#How_to_Choose_the_Right_Severity [^]