Openbravo Issue Tracking System - Localization Pack: Spain | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0023156 | Localization Pack: Spain | AEAT 340 | public | 2013-02-25 11:13 | 2013-02-25 13:28 |
| Reporter | egoitz | ||||
| Assigned To | vmromanos | ||||
| Priority | high | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| Merge Request Status | |||||
| Regression date | |||||
| Regression introduced by commit | |||||
| Regression level | |||||
| Review Assigned To | |||||
| Support ticket | |||||
| OBNetwork customer | |||||
| Regression introduced in release | |||||
| Summary | 0023156: The 340 report should be designed to be able to define new javas to be executed for periods | ||||
| Description | Right now is hardcoded with java should be executed depending the year. A better design should be to have the possibility to define which java to use on each year. It will simplify the maintenance. In this way you could publish a new module for a new year instead of publishing a new release of the module. | ||||
| Steps To Reproduce | - | ||||
| Proposed Solution | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2013-02-25 11:13 | egoitz | New Issue | |||
| 2013-02-25 11:13 | egoitz | Assigned To | => vmromanos | ||
| 2013-02-25 13:25 | psanjuan | Summary | The 340 report should be designed to be ablo to define new javas to be executed for periods => The 340 report should be designed to be able to define new javas to be executed for periods | ||
| There are no notes attached to this issue. |