Project

General

Profile

Actions

Defect #6843

closed

REST API Does Not Include Target Version

Defect #6843: REST API Does Not Include Target Version

Added by Jeremy Walker about 16 years ago. Updated about 15 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
REST API
Target version:
-
Resolution:
Cant reproduce
Affected version:

Description

The REST API for issues does not include the target version of the issue. This is a surprising omission given that the XML returned for issues contains just about everything else available on the normal issues page.

Updated by Jean-Philippe Lang about 16 years ago Actions #1

  • Status changed from New to Closed
  • Resolution set to Cant reproduce

In trunk and 1.0.1, the target version is present in /issues.xml and /issues/1.xml.

See:
  • source:/tags/1.0.1/app/views/issues/index.xml.builder#L13
  • source:/tags/1.0.1/app/views/issues/show.xml.builder#L11

Note that the tag is omitted if target version is not set.

Updated by Jeremy Walker about 16 years ago Actions #2

Ah sorry, my mistake (must have had some un-versioned records without realizing it).

Updated by Jeremy Walker about 16 years ago Actions #3

Stupid question though: why is it called "fixed_version" in the API (even for issues with status New, which clearly aren't fixed), but "target version" (which makes much more sense universally) in normal Redmine?

Updated by Jean-Philippe Lang about 16 years ago Actions #4

"Target version" is the new display name for this property, but it's still named fixed_version internally and thus in the API.

Updated by Jeremy Walker about 16 years ago Actions #5

Ahhhh

Updated by fasdfasd fasdfasdf about 15 years ago Actions #6

SPAM

Actions

Also available in: PDF Atom