Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0017291Openbravo ERPA. Platformpublic2011-05-20 08:172022-02-01 08:08
Reporterelopio 
Assigned ToTriage Platform Base 
PrioritylowSeveritymajorReproducibilityalways
StatusacknowledgedResolutionopen 
PlatformOS5OS Version
Product Version 
Target VersionpiFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0017291: Inconsistent success message
DescriptionSome success messages have a title, and some others don't.

For example, on Goods Shipment, after creating lines from a sales order, a message with title "Success" appears.
After completing it, the same message but without title appears.
Steps To ReproduceCreate a Sales Order
Add some Lines
Complete the order.
(message without title appears)
Create a Goods Shipment header
Click create lines from and select the previously created order)
(message with title appears)
Proposed SolutionFor consistency, all messages should have a title.

There are some messages like the one in create inventory count list whose title is "Process completed successfully" and then comes a message. For those cases, I guess that the right title would be "Success".
Additional Information
Tagsconsistency, testability
Relationships
related to feature request 0008248 new rgoris Success message shown inconsistently 
related to feature request 0013825 new Triage Platform Base All message box titles should be the same: Error, Warning, Process Succeeded, Information ... 
related to design defect 0017292pi acknowledged Triage Platform Base Successful messages should end with a period. 
Attached Filespng InconsistentMessages.PNG (80,370) 2011-05-20 17:31
https://issues.openbravo.com/file_download.php?file_id=4065&type=bug
png
Issue History
Date ModifiedUsernameFieldChange
2011-05-20 08:17elopioNew Issue
2011-05-20 08:17elopioAssigned To => elopio
2011-05-20 08:17elopioModules => Core
2011-05-20 08:17elopioOBNetwork customer => No
2011-05-20 08:17elopioTag Attached: testability
2011-05-20 08:17elopioTag Attached: consistency
2011-05-20 08:17elopioRelationship addedrelated to 0008248
2011-05-20 08:20elopioNote Added: 0037263
2011-05-20 09:41elopioAssigned Toelopio =>
2011-05-20 09:41elopioProposed Solution updated
2011-05-20 10:07elopioRelationship addedrelated to 0013825
2011-05-20 17:31plujanFile Added: InconsistentMessages.PNG
2011-05-20 17:59plujanNote Added: 0037293
2011-05-20 17:59plujanAssigned To => alostale
2011-05-20 17:59plujanPriorityhigh => immediate
2011-05-20 17:59plujanSeverityminor => major
2011-05-20 17:59plujanCategoryB. User interface => A. Platform
2011-05-23 07:58alostaleRelationship addedrelated to 0017292
2011-05-23 10:47psarobePriorityimmediate => urgent
2011-05-23 10:47psarobeStatusnew => acknowledged
2012-03-28 17:33alostaleNote Added: 0046851
2012-03-28 17:33alostaleTypedefect => design defect
2012-09-24 21:18AugustoMauchNote Added: 0052443
2012-09-24 21:18AugustoMauchPriorityurgent => low
2012-09-24 21:18AugustoMauchStatusacknowledged => scheduled
2017-03-31 14:36alostaleStatusscheduled => acknowledged
2017-04-10 14:34alostaleAssigned Toalostale => platform
2022-02-01 08:08alostaleAssigned Toplatform => Triage Platform Base

Notes
(0037263)
elopio   
2011-05-20 08:20   
Priority set to high because 2.50 version is still with a lot of similar inconsistencies. This is a good moment to change it in 3.0.
In addition, integration selenium testing is harder when things are not consistent. A special function has to be made for every case that doesn't follow the norm.
(0037293)
plujan   
2011-05-20 17:59   
Raised priority to immediate since it breaks smoke tests.
(0046851)
alostale   
2012-03-28 17:33   
Setting it as design defect because it might require to review all process messages.
(0052443)
AugustoMauch   
2012-09-24 21:18   
Impact: low
Plan: long