Defect #19065
API: issue details created_on timestamp not formatted as expected
Status: | Closed | Start date: | ||
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | % Done: | 0% | ||
Category: | REST API | |||
Target version: | 2.6.2 | |||
Resolution: | Fixed | Affected version: | 2.6.1 |
Description
Hello, it seems like there is something wrong with create_on format for journal entry in the latest 2.6-stable when data it retrieved using API. The time is not in ISO 8601 for journal entry, but the time fields in the issue details are still in ISO 8601. See attached screenshots.
Related issues
Associated revisions
Fixed that timestamps may not be formatted as expected in XML responses (#19065).
History
#1
Updated by Ruslan Kabalin almost 6 years ago
I think timestamp format in journal entries should match the one in issue details (should be ISO 8601).
#2
Updated by Toshi MARUYAMA almost 6 years ago
- Category set to REST API
- Target version set to 2.6.2
#3
Updated by Jean-Philippe Lang almost 6 years ago
- Subject changed from api: issue details created_on timestamp inconsistency to API: issue details created_on timestamp not formatted as expected
- Status changed from New to Resolved
- Assignee set to Jean-Philippe Lang
- Resolution set to Fixed
Fixed in r14015, thanks for pointing this out.
#4
Updated by Jean-Philippe Lang almost 6 years ago
- Status changed from Resolved to Closed
#5
Updated by Toshi MARUYAMA almost 6 years ago
- Duplicated by Defect #19227: Users.xml broken added