Opened 12 years ago
Last modified 7 months ago
#10916 new defect
The date/time fields in Custom Query has problem with babel date format. — at Initial Version
| Reported by: | Genie | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | next-stable-1.6.x |
| Component: | i18n | Version: | 1.0 |
| Severity: | normal | Keywords: | babel parse_date format_date |
| Cc: | Jun Omae | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Hi~
The date/time fields in Custom Query has problem with babel date format.
The babel date format can contains dot ., and can end with dot ..
2012. 1. 1. | babel date format on Korean locale |
The date/time fields created and modified in Custom Query
can specifying a value containing two dates separated by two dots ...
created=2011-01-01..2012-01-01 | query tickets created in 2011 with ISO 8601 format |
If we query tickets created in 2011 on Korean locale,
the result of query are fail because three dots ....
created=2011. 1. 1...2012. 1. 1. | query tickets created in 2011 with babel date format on Korean |
Note:
See TracTickets
for help on using tickets.
