Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
| ID | |||||||||||
| 0017291 | |||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||||
| design defect | [Openbravo ERP] A. Platform | major | always | 2011-05-20 08:17 | 2022-02-01 08:08 | ||||||
| Reporter | elopio | View Status | public | ||||||||
| Assigned To | Triage Platform Base | ||||||||||
| Priority | low | Resolution | open | Fixed in Version | |||||||
| Status | acknowledged | Fix in branch | Fixed in SCM revision | ||||||||
| Projection | none | ETA | none | Target Version | pi | ||||||
| OS | Any | Database | Any | Java version | |||||||
| OS Version | Database version | Ant version | |||||||||
| Product Version | SCM revision | ||||||||||
| Merge Request Status | |||||||||||
| Review Assigned To | |||||||||||
| OBNetwork customer | No | ||||||||||
| Web browser | |||||||||||
| Modules | Core | ||||||||||
| Support ticket | |||||||||||
| Regression level | |||||||||||
| Regression date | |||||||||||
| Regression introduced in release | |||||||||||
| Regression introduced by commit | |||||||||||
| Triggers an Emergency Pack | No | ||||||||||
| Summary | 0017291: Inconsistent success message | ||||||||||
| Description | Some 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 Reproduce | Create 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 Solution | For 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". | ||||||||||
| Tags | consistency, testability | ||||||||||
| Attached Files |  InconsistentMessages.PNG [^] (80,370 bytes) 2011-05-20 17:31
| ||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
||||||||||||||||||||||
|
||||||||||||||||||||||
 Relationships |
|
Notes |
|
|
(0037263) elopio (viewer) 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 (viewer) 2011-05-20 17:59 |
Raised priority to immediate since it breaks smoke tests. |
|
(0046851) alostale (viewer) 2012-03-28 17:33 |
Setting it as design defect because it might require to review all process messages. |
|
(0052443) AugustoMauch (administrator) 2012-09-24 21:18 |
Impact: low Plan: long |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2011-05-20 08:17 | elopio | New Issue | |
| 2011-05-20 08:17 | elopio | Assigned To | => elopio |
| 2011-05-20 08:17 | elopio | Modules | => Core |
| 2011-05-20 08:17 | elopio | OBNetwork customer | => No |
| 2011-05-20 08:17 | elopio | Tag Attached: testability | |
| 2011-05-20 08:17 | elopio | Tag Attached: consistency | |
| 2011-05-20 08:17 | elopio | Relationship added | related to 0008248 |
| 2011-05-20 08:20 | elopio | Note Added: 0037263 | |
| 2011-05-20 09:41 | elopio | Assigned To | elopio => |
| 2011-05-20 09:41 | elopio | Proposed Solution updated | |
| 2011-05-20 10:07 | elopio | Relationship added | related to 0013825 |
| 2011-05-20 17:31 | plujan | File Added: InconsistentMessages.PNG | |
| 2011-05-20 17:59 | plujan | Note Added: 0037293 | |
| 2011-05-20 17:59 | plujan | Assigned To | => alostale |
| 2011-05-20 17:59 | plujan | Priority | high => immediate |
| 2011-05-20 17:59 | plujan | Severity | minor => major |
| 2011-05-20 17:59 | plujan | Category | B. User interface => A. Platform |
| 2011-05-23 07:58 | alostale | Relationship added | related to 0017292 |
| 2011-05-23 10:47 | psarobe | Priority | immediate => urgent |
| 2011-05-23 10:47 | psarobe | Status | new => acknowledged |
| 2012-03-28 17:33 | alostale | Note Added: 0046851 | |
| 2012-03-28 17:33 | alostale | Type | defect => design defect |
| 2012-09-24 21:18 | AugustoMauch | Note Added: 0052443 | |
| 2012-09-24 21:18 | AugustoMauch | Priority | urgent => low |
| 2012-09-24 21:18 | AugustoMauch | Status | acknowledged => scheduled |
| 2017-03-31 14:36 | alostale | Status | scheduled => acknowledged |
| 2017-04-10 14:34 | alostale | Assigned To | alostale => platform |
| 2022-02-01 08:08 | alostale | Assigned To | platform => Triage Platform Base |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |