Openbravo Issue Tracking System - Mantis @ OB | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0007933 | Mantis @ OB | Others | public | 2009-03-04 10:42 | 2018-04-06 18:07 |
| Reporter | plujan | ||||
| Assigned To | gorka_gil | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | out of date | ||
| Platform | OS | 5 | OS Version | ||
| Merge Request Status | |||||
| Review Assigned To | |||||
| OBNetwork customer | |||||
| Summary | 0007933: Fix in branch for all projects are the same as Openbravo ERP | ||||
| Description | Working on a different project (Localization, QA, Web, Mantis@OB) when resolving am issue I see the same "Fix in branch" options. For example, "pi" option may have no sense for projects other than Openbravo ERP. | ||||
| Steps To Reproduce | |||||
| Proposed Solution | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2009-03-04 10:42 | plujan | New Issue | |||
| 2009-11-18 18:20 | jpabloae | Assigned To | => jpabloae | ||
| 2011-08-24 12:58 | jpabloae | Assigned To | jpabloae => gorka_gil | ||
| 2018-04-06 18:07 | shuehner | Note Added: 0103721 | |||
| 2018-04-06 18:07 | shuehner | Status | new => closed | ||
| 2018-04-06 18:07 | shuehner | Resolution | open => out of date | ||
| Notes | |||||
|
|
|||||
|
|
||||