Openbravo Issue Tracking System - Openbravo ERP  | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update | 
| 0024103 | Openbravo ERP | 09. Financial management | public | 2013-06-17 22:55 | 2013-06-17 22:55 | 
| Reporter | itadmin | ||||
| Assigned To | dmiguelez | ||||
| Priority | high | Severity | major | Reproducibility | always | 
| Status | new | Resolution | open | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| 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 | 0024103: It is possible to close a year when next fiscal period/year is inactivated | ||||
| Description | Having two fiscal periods; P1 and P2. Inactivate P2. Then close year = P1. Still possible though P2 is not active. This is a result of inadequate use case modeling.  | ||||
| Steps To Reproduce | see above | ||||
| Proposed Solution | make not possible to close year if next period is inactive. Must be created and active. | ||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2013-06-17 22:55 | itadmin | New Issue | |||
| 2013-06-17 22:55 | itadmin | Assigned To | => dmiguelez | ||
| 2013-06-17 22:55 | itadmin | Modules | => Core | ||
| 2013-06-17 22:55 | itadmin | Triggers an Emergency Pack | => No | ||
| There are no notes attached to this issue. |