Back to bug 42747
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| cluster15 | 2012-03-21 06:31:13 UTC | Attachment #53333 Attachment description | test case database caontaining currecny field wrongly interpretated | test case of a database containing currency fields in forms which are wrongly interpretated |
| cluster15 | 2012-03-21 06:35:56 UTC | Priority | medium | high |
| Version | LibO 3.4.4 release | LibO 3.5.1 Release | ||
| Severity | normal | critical | ||
| serval2412 | 2012-03-24 00:32:16 UTC | Status | UNCONFIRMED | NEEDINFO |
| CC | serval2412 | |||
| Ever confirmed | 0 | 1 | ||
| causb | 2012-04-08 01:54:23 UTC | CC | causb | |
| dr | 2012-07-24 19:46:38 UTC | CC | dr | |
| cluster15 | 2012-07-30 13:00:31 UTC | Status | NEEDINFO | UNCONFIRMED |
| Ever confirmed | 1 | 0 | ||
| robert | 2012-08-03 17:43:29 UTC | Priority | high | medium |
| Status | UNCONFIRMED | NEW | ||
| CC | robert | |||
| Ever confirmed | 0 | 1 | ||
| Severity | critical | normal | ||
| cluster15 | 2014-02-17 15:44:40 UTC | Version | 3.5.1 release | 4.1.4.2 release |
| serval2412 | 2014-02-17 16:46:34 UTC | Version | 4.1.4.2 release | 3.4.4 release |
| cluster15 | 2014-02-20 16:08:54 UTC | Version | 3.4.4 release | 3.4.1 release |
| cluster15 | 2014-02-20 16:09:25 UTC | Version | 3.4.1 release | 3.4.4 release |
| serval2412 | 2014-07-01 05:45:18 UTC | CC | caolanm, lionel | |
| Severity | normal | major | ||
| lionel | 2014-07-01 06:27:26 UTC | Version | 3.4.4 release | 3.3.4 release |
| libreoffice-commits | 2014-07-01 12:32:06 UTC | Whiteboard | target:4.4.0 | |
| caolanm | 2014-07-01 12:35:39 UTC | Status | NEW | RESOLVED |
| Resolution | --- | FIXED | ||
| Assignee | libreoffice-bugs | caolanm | ||
| libreoffice-commits | 2014-07-01 19:49:07 UTC | Whiteboard | target:4.4.0 | target:4.4.0 target:4.3.0.2 |
| libreoffice-commits | 2014-07-02 21:48:41 UTC | Whiteboard | target:4.4.0 target:4.3.0.2 | target:4.4.0 target:4.3.0.2 target:4.2.6 |
Back to bug 42747
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.