Changes between Initial Version and Version 2 of Ticket #1001


Ignore:
Timestamp:
Dec 20, 2006 12:52:33 PM (8 years ago)
Author:
athomas
Comment:

This could be added to AccountManagerPlugin or perhaps user session introspection could be added to XmlRpcPlugin.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1001

    • Property Status changed from new to assigned
    • Property Owner changed from athomas to coderanger
  • Ticket #1001 – Description

    initial v2  
    1 Currrently when you query for a ticket's information you get all the attributes on it, however I have no way to identify a user uniquely besides their username which is only relevant on the server. So I can't contact that user through his email information or have a local application specific user store that can query this information for particular users. So if I had this interface I could get a user's full name(first and last), and at least his email. I assume the UserManager plugin could extend the attributes available for a user and maybe even add more calls like a user.getAll() 
     1Currrently when you query for a ticket's information you get all the attributes on it, however I have no way to identify a user uniquely besides their username which is only relevant on the server. So I can't contact that user through his email information or have a local application specific user store that can query this information for particular users. So if I had this interface I could get a user's full name(first and last), and at least his email. I assume the AccountManagerPlugin could extend the attributes available for a user and maybe even add more calls like a user.getAll()