Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0041229Openbravo ERPA. Platformpublic2019-07-02 13:412022-02-01 08:07
Reporterplujan 
Assigned ToTriage Platform Base 
PrioritynormalSeveritytrivialReproducibilityhave not tried
StatusfeedbackResolutionopen 
PlatformOS5OS Version
Product Versionmain 
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
Summary0041229: [19Q3] Activation of the instance resets the maturity level to search modules/updates
DescriptionThe fix for 0040385 prevents the error described in the issue to happen, but does not change the fact that the maturity levels were changed with no apparent reason.
Steps To Reproduce1. Using a community instance that requires at least one update for a Commercial module that is present only in "QA" or "QA Approved" maturity status (e.g. an active instance after an install source) seek for updates.
2. After the updates are found, try to install them. As expected, a message saying that the lack of an activation does not allow the process to be completed is shown.
3. Close the window and activate the instance via the Instance Activation window
4. Return to the Module Management and search for updates. The update previously shown now does not appear. The reason is the Maturity Level has been changed to "Confirmed Stable"
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to defect 0040385 closed alostale [PR19Q1] Activating an instance after installing modules may create an incomplete update 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2019-07-02 13:41plujanNew Issue
2019-07-02 13:41plujanAssigned To => platform
2019-07-02 13:41plujanModules => Core
2019-07-02 13:41plujanTriggers an Emergency Pack => No
2019-07-02 13:42plujanRelationship addedrelated to 0040385
2020-04-13 10:52alostaleNote Added: 0119134
2020-04-13 10:52alostaleStatusnew => feedback
2020-04-13 10:52alostaleTypedefect => design defect
2020-04-13 10:52alostaleAssigned Toplatform => plujan
2021-07-21 13:17plujanAssigned Toplujan =>
2021-07-21 13:17plujanAssigned To => platform
2021-07-21 13:18plujanNote Added: 0130663
2022-02-01 08:07alostaleAssigned Toplatform => Triage Platform Base

Notes
(0119134)
alostale   
2020-04-13 10:52   
This is done by current design. Instance activation changes accepted maturity status to CS (as community instances can only restrict it to QAA at most).

In case you think this should be changed, please comment and agree first with DME.
(0130663)
plujan   
2021-07-21 13:18   
please do not change the assigned user when asking the reporter for feedback