Feature #7487

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

Added by Alex Last over 8 years ago. Updated over 1 year ago.

Status:NewStart date:2011-01-29
Priority:NormalDue date:
Assignee:Jean-Philippe Lang% Done:

0%

Category:REST API
Target version:-
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.

History

#1 Updated by Etienne Massip over 8 years ago

  • Tracker changed from Defect to Feature

#2 Updated by Terence Mill almost 8 years ago

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

#3 Updated by Terence Mill almost 8 years ago

related to #1739

#4 Updated by Alex Last over 6 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?..

#5 Updated by Alex Last over 1 year 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.

Also available in: Atom PDF