MantisBT - TestLink
View Issue Details
0002408TestLinkAPI - XMLRPCpublic2009-04-21 08:242010-08-31 20:28
normalfeature requestN/A
1.8 RC 3 
1.9 Beta 5 
0002408: Relation between internal testcaseid,testplanid,projectid,buildid and web based ids in testlink
Presently unless we export the XML file we cannot view the internal testcaseids for the API calls. I do not know if any relation exists between the web based ids and the internal ids. Also I could not find the projectid, buildid and the testplanid from the XML file. It would be a nice feature to be able to view them or guess the internal ids from the web based ids for the API calls.
png testplan.png (100,709) 2009-04-25 03:58

png testproject1.png (112,772) 2009-04-25 03:59

jpg mnu.jpg (31,971) 2010-06-03 20:45
Issue History
2009-04-21 08:24abadveNew Issue
2009-04-21 16:05fmanNote Added: 0006487
2009-04-24 06:18abadveNote Added: 0006556
2009-04-24 19:27fmanNote Added: 0006580
2009-04-24 19:28fmanStatusnew => feedback
2009-04-25 03:58abadveTag Attached: Attachment
2009-04-25 03:58abadveFile Added: testplan.png
2009-04-25 03:59abadveFile Added: testproject1.png
2009-04-25 04:02abadveNote Added: 0006592
2009-07-09 04:51mhavlatStatusfeedback => new
2009-07-09 23:27fmanNote Added: 0007488
2009-07-09 23:27fmanStatusnew => assigned
2009-07-09 23:27fmanAssigned To => fman
2009-07-27 23:55fmanNote Added: 0007649
2010-06-03 20:41fmanNote Added: 0010223
2010-06-03 20:45fmanFile Added: mnu.jpg
2010-06-03 20:46fmanNote Added: 0010224
2010-06-03 20:47fmanStatusassigned => resolved
2010-06-03 20:47fmanFixed in Version => 1.9 Beta 5
2010-06-03 20:47fmanResolutionopen => fixed
2010-08-31 20:28fmanNote Added: 0011136
2010-08-31 20:28fmanStatusresolved => closed
2013-04-25 17:30fmanCategoryTL API => XMLRPC API
2013-04-25 17:30fmanCategoryXMLRPC API => API - XMLRPC

2009-04-21 16:05   
>> Also I could not find the projectid, buildid and the testplanid from the XML >> file
you got this info at user interface level.

>> the internal testcaseids for the API calls
All API functions must be refactored to allow use of internal or external id
2009-04-24 06:18   
Thanks for your reply. Can you tell me please how to refactor the API calls to allow use of external id?

I am still not clear how to get the projectidm buildid and testplanid information.
Can you please send a working example or screen snapshot?
2009-04-24 19:27   
// --------------------------------------------------------------------------------------
/** [API] */

/** XML-RPC API availability (disabled by default) */
$tlCfg->api->enabled = TRUE; //FALSE;

// used to display API ID info in the *View pages
$tlCfg->api->id_format = "[ID: %s ]";

you will see a new icon (brick) on several pages that will aloow you to display internal ID
2009-04-25 04:02   

Thanks for your reply. I already had these two lines enabled in the config file. I have sent you snapshot images (attached testplan.png file and testproject1.png file) of the test plan and test project page showing the ids in my installation.
When I use these ids in any of the API calls reportTC result for example I get errors like projectid does not exist and so on. I now need to know which id to use in the API code.
2009-07-09 23:27   
excuse me for long time before replying, I will try to do some tests and give you asnwer ASAP
2009-07-27 23:55   
For test case you can get internal id when navigating tree, you can see at least on firefox id on footer.

Anyway on 1.9 we have refactored calls in order to allow you to use EXTERNAL ID.
2010-06-03 20:41   
enabled context menu on right button to display API ID, on test spec tree.
see attached image
2010-06-03 20:46   
Reminder sent to: asimon, Julian

I've made first implementation of context menu on tree.
2010-08-31 20:28   
Release BETA 6 - 20100831