Project

General

Profile

Actions

Feature #7487

open

change "author" field format to have login, fname, lname instead of ambiguous "full name"

Added by Alex Last about 13 years ago. Updated almost 6 years ago.

Status:
New
Priority:
Normal
Category:
REST API
Target version:
-
Start date:
2011-01-29
Due date:
% Done:

0%

Estimated time:
Resolution:

Description

"author" and "assigned_to" fields included in "get issues" XML response have user full name under ambiguous "name" attribute:
<author name="Alexey Java" id="421"/>
<assigned_to name="Alexey Java" id="421"/>

can we have several separate attributes for "author" and "assigned_to" instead:
  • login
  • id
  • firstName
  • lastName
    ?

this would simplify the response parsing. I can't reconstruct firstName and lastName from this response without making a separate "getUsers()" call to the server, which seems unnecessary.

Actions #1

Updated by Etienne Massip about 13 years ago

  • Tracker changed from Defect to Feature
Actions #2

Updated by Terence Mill over 12 years ago

It should be possible to set author by all attributes only which have key property (login, email, internal id)

Actions #3

Updated by Terence Mill over 12 years ago

related to #1739

Actions #4

Updated by Alex Last over 10 years ago

this is about the response from the server, not about setting values by the clients. we can't properly parse the server response from this combined "name" which actually contains a combination of first name, space, then last name - what if they contain spaces in names?..

Actions #5

Updated by Alex Last almost 6 years ago

if anyone is working on REST API, is it possible to make this improvement? this can be made in a backward-compatible manner by adding new fields to the response.

Actions

Also available in: Atom PDF