Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Openbravo ERP] A. Platformtrivialhave not tried2019-07-02 13:412021-07-21 13:18
ReporterplujanView Statuspublic 
Assigned Toplatform 
PrioritynormalResolutionopenFixed in Version
StatusfeedbackFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionmainSCM revision 
Review Assigned To
Web browser
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0041229: [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"
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to defect 0040385 closedalostale [PR19Q1] Activating an instance after installing modules may create an incomplete update 

-  Notes
alostale (developer)
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.
plujan (manager)
2021-07-21 13:18

please do not change the assigned user when asking the reporter for feedback

- Issue History
Date Modified Username Field Change
2019-07-02 13:41 plujan New Issue
2019-07-02 13:41 plujan Assigned To => platform
2019-07-02 13:41 plujan Modules => Core
2019-07-02 13:41 plujan Triggers an Emergency Pack => No
2019-07-02 13:42 plujan Relationship added related to 0040385
2020-04-13 10:52 alostale Note Added: 0119134
2020-04-13 10:52 alostale Status new => feedback
2020-04-13 10:52 alostale Type defect => design defect
2020-04-13 10:52 alostale Assigned To platform => plujan
2021-07-21 13:17 plujan Assigned To plujan =>
2021-07-21 13:17 plujan Assigned To => platform
2021-07-21 13:18 plujan Note Added: 0130663

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker