The user.get_details API provides limited information. The customer only requires created date, but I would suggest also adding last checkin while we're messing in that part of the code. We need to provide this in an scriptable form using a SQL query as an interim step to full support in API.
API is bret.
created is easy to add, but what exactly do you mean by "last checkin"? you mean last login?
correct. last login.
Customer Facing now "NO" Docs status now tracked by bug 147140
Ok, it's now in webdev. Test plan: use web api unit tests
updating hours worked
Done TEST PLAN Review the Documentation section of the rhn (hosted) release notes and ensure this change is mentioned. Setting to ON_DEV
Sorry, put this info in the wrong bug. See bug #147140
To actually test this bug, what we really want is a perl script that can make the API call against prod, and make the API call against QA, and the we can compare the results and ensure that they differ appropriately. Bret, can you provide such a script relatively easily?
Created attachment 111559 [details] simple python test script This is a simple python script... usage is: python get-details-test.py [username] [password] [env-hostname] where env-hostname is something like rhn.webqa.redhat.com, and username & password identify a user both on rhn.redhat.com as well as env-hostname. Not really sure why we're testing prod and the difference, probably just need to test env-hostname and make sure we're getting back what we expect, but you ask and I provide :)
The script passed with success. Thank you bretm.
mass move: PROD_READY --> CLOSED:CURRENTRELEASE