Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0003359 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| feature request | [Openbravo ERP] B. User interface | minor | always | 2007-07-04 03:20 | 2008-07-01 19:44 | |||
| Reporter | plujan | View Status | public | |||||
| Assigned To | user71 | |||||||
| Priority | normal | Resolution | fixed | Fixed in Version | 2.40 | |||
| Status | closed | Fix in branch | Fixed in SCM revision | |||||
| Projection | none | ETA | none | Target Version | 2.40 | |||
| 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 | 0003359: Incorrect message saving a Completed Purchase Order | |||||||
| Description | Description: Incorrect message saving a Completed Purchase Order with no changes Enviroment: OS: Windows XP SP2 DB: Oracle XE Browser: FF2 Openbravo: 2.31 Beta Language: English Steps: 1. Go Procurement Management > Transactions > Purchase Order 2. Create a new Purchase order with valid data 3. Move to Order Lines Tab 4. The empty grid appears 5. Create a new Order Line 6. Move back to Purchase Order Tab 7. Complete the order 8. Try to save the order, making no changes 9. An incorrect message appears (see attach) because there was no changes | |||||||
| Tags | No tags attached. | |||||||
| Attached Files | ||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0003891) cromero (viewer) 2007-10-03 19:41 edited on: 2008-06-12 09:26 |
Logged In: YES user_id=1500614 Originator: NO This should be a feature request for "Change Management". Message is correct, the problem is that we should control if there have been changesin order to enable or not the update. Carlos Romero Openbravo Team |
|
(0006948) user71 2005-06-01 00:00 edited on: 2008-06-12 09:44 |
This bug was originally reported in SourceForge bug tracker and then migrated to Mantis. You can see the original bug report in: https://sourceforge.net/support/tracker.php?aid=1747437 [^] |
|
(0008117) pjuvara (viewer) 2008-07-01 19:43 |
I believe this is now solved in 2.40. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2008-07-01 19:43 | pjuvara | Status | new => closed |
| 2008-07-01 19:43 | pjuvara | Note Added: 0008117 | |
| 2008-07-01 19:43 | pjuvara | Resolution | open => fixed |
| 2008-07-01 19:44 | pjuvara | OBNetwork customer | => No |
| 2008-07-01 19:44 | pjuvara | Fixed in Version | => 2.40 |
| 2008-07-01 19:44 | pjuvara | Target Version | => 2.40 |
| 2008-07-01 19:44 | pjuvara | Description Updated | |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |