Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0022576 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [Openbravo ERP] Z. Others | major | have not tried | 2012-12-14 09:11 | 2015-04-07 08:37 | |||
| Reporter | ioritzCia | View Status | public | |||||
| Assigned To | iciordia | |||||||
| Priority | urgent | Resolution | out of date | Fixed in Version | ||||
| Status | closed | Fix in branch | Fixed in SCM revision | |||||
| Projection | none | ETA | none | Target Version | ||||
| OS | Linux 32 bit | Database | PostgreSQL | Java version | 1.6.0_22 | |||
| OS Version | Ubuntu 10.04 | Database version | 8.4 | Ant version | 1.7.1 | |||
| 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 | 0022576: Issue 21938: try-api fails. | |||||||
| Description | Due to this issue: - https://issues.openbravo.com/view.php?id=21938 [^] I have to make an api change. This is the api change: - https://code.openbravo.com/erp/devel/try/diff/e70e0e5e76a2/src-db/database/sourcedata/AD_COLUMN.xml [^] I have pushed the change to try, this is the failure: - http://builds.openbravo.com/view/try/job/try-api/1212/console [^] - The change is the following: The column FIN_Payment.paymentDate changes from nullable to mandatory. - The change is needed due to the following reason: The system only allows you to insert a payment without payment date if the user deletes the date. It should not leave you do it. A payment without payment date cannnot be posted. - The risk of the api change is very low to the following reason: There is no logical business logic where a payment should not have a payment date. Someone could have developed by error a module where a payment can be null but the module most surely will work if it is not null. A buildvalidation has been developed in order to avoid people with payments with null payment date to update to the instance prior to having solved the problem. | |||||||
| Steps To Reproduce | none. | |||||||
| Tags | No tags attached. | |||||||
| Attached Files | ||||||||
Relationships [ Relation Graph ]
[ Dependency Graph ]
|
||||||||
|
||||||||
Notes |
|
|
(0054952) iciordia (viewer) 2012-12-14 19:51 |
Ioritz, as agreed, please research on our customer base to validate that the risk is low (although it makes no sense to have payments without payment_date, we need to confirm that there are no cases in which custom modules generate payments without payment_date) -> if that's the case then we should deploy this change very carefully. Thanks, Ismael |
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2012-12-14 09:11 | ioritzCia | New Issue | |
| 2012-12-14 09:11 | ioritzCia | Assigned To | => dmiguelez |
| 2012-12-14 09:11 | ioritzCia | Modules | => Core |
| 2012-12-14 09:11 | ioritzCia | OBNetwork customer | => No |
| 2012-12-14 09:11 | ioritzCia | Triggers an Emergency Pack | => No |
| 2012-12-14 09:12 | ioritzCia | Assigned To | dmiguelez => iciordia |
| 2012-12-14 09:12 | ioritzCia | Status | new => feedback |
| 2012-12-14 19:51 | iciordia | Note Added: 0054952 | |
| 2013-01-09 10:11 | ioritzCia | Priority | immediate => urgent |
| 2013-01-09 10:11 | ioritzCia | Severity | critical => major |
| 2013-01-16 11:16 | ioritzCia | Relationship added | related to 0021938 |
| 2015-04-07 08:37 | alostale | Status | feedback => closed |
| 2015-04-07 08:37 | alostale | Resolution | open => out of date |
| Copyright © 2000 - 2009 MantisBT Group |