Project

General

Profile

Actions

Defect #19065

closed

API: issue details created_on timestamp not formatted as expected

Added by Ruslan Kabalin about 9 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Normal
Category:
REST API
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

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.


Files

rm25_api_issue.png (53.4 KB) rm25_api_issue.png 2.5.3 Ruslan Kabalin, 2015-02-09 16:01
rm26_api_issue.png (46.1 KB) rm26_api_issue.png latest 2.6-stable branch (0c1a287696) Ruslan Kabalin, 2015-02-09 16:10

Related issues

Has duplicate Redmine - Defect #19227: Users.xml brokenClosed

Actions
Actions #1

Updated by Ruslan Kabalin about 9 years ago

I think timestamp format in journal entries should match the one in issue details (should be ISO 8601).

Actions #2

Updated by Toshi MARUYAMA about 9 years ago

  • Category set to REST API
  • Target version set to 2.6.2
Actions #3

Updated by Jean-Philippe Lang about 9 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.

Actions #4

Updated by Jean-Philippe Lang about 9 years ago

  • Status changed from Resolved to Closed
Actions #5

Updated by Toshi MARUYAMA about 9 years ago

Actions

Also available in: Atom PDF