Need help locating RPC plugin in trial Jira
I’m working on connecting TestLink with my Jira trial instance but running into problems. When I go to the system configuration area, I can’t seem to locate the RPC plugin anywhere.
I’ve checked through the admin panel and searched in various settings sections but no luck so far. Is this plugin available in the trial version? Maybe it’s hidden somewhere I haven’t looked yet.
Has anyone successfully set up this integration before? I’m specifically trying to get TestLink talking to Jira but without the RPC functionality enabled, nothing seems to work properly.
Any guidance on where exactly this plugin should appear would be really helpful. Thanks in advance!
You won’t find the RPC plugin in Jira’s interface - it’s not a real Jira plugin. TestLink just uses XML-RPC calls to talk to Jira through the REST API.
You need to enable API access in Jira. Go to Administration > System > General Configuration and turn on REST API. Then create API tokens for auth.
But honestly? Direct TestLink-Jira integration sucks. I’ve done this multiple times and it’s brittle as hell - breaks constantly with updates.
Use an automation platform instead. Skip TestLink’s built-in connector and create workflows that sync test results, make issues, and update statuses between both systems.
You get way more control and reliability. Custom triggers, business logic, other tools in your workflow - the works. When either system updates, your integration won’t randomly die.
I’ve watched teams save weeks of troubleshooting by ditching native integrations.
For reliable automation, check out Latenode: https://latenode.com
The XML-RPC endpoint works in trial versions, but there’s a config step everyone misses. Check that application access is enabled under User Management settings. Without it, TestLink auth fails silently even when the endpoint responds. I hit this exact problem last year during a trial setup. Connection would timeout or throw auth errors despite having the right URLs and credentials. The fix was enabling application access for external integrations in security settings. Also double-check your TestLink config - make sure you’re using the right Jira project key format and that the user account has proper permissions on both systems. Sometimes it looks like it’s working but crashes when creating or updating issues because of permission issues. If you’re still stuck, test the XML-RPC endpoint directly with Postman first to see if it’s a Jira config problem or something with TestLink’s implementation.
had a similar issue too! the rpc endpoint is def there but testlink can be picky. try adding /plugins/servlet/xmlrpc to your jira base url in testlink settings. also, make sure your user has jira admin permissions, otherwise it might not work right.
XML-RPC is enabled by default in Jira trials. Just hit yourdomain.atlassian.net/rpc/xmlrpc (cloud) or yourserver/rpc/xmlrpc (server).
Here’s the problem - TestLink’s Jira integration is a total nightmare. I’ve watched it break after minor Jira updates, auth changes, even field config tweaks.
Don’t mess with XML-RPC calls hoping TestLink behaves. Build your own automation bridge instead. Pull test data from TestLink, transform it how you want, then push clean issues into Jira.
This handles edge cases way better. Failed tests become bugs with proper priority. Passed tests update story status. Different test types can hit different Jira projects.
When it breaks, you’re debugging your workflow - not digging through TestLink’s connection logs.
I’ve done this with dozens of tool integrations. Way more reliable than hoping two systems play nice forever.
Check out Latenode for this stuff: https://latenode.com
Jira has RPC built in by default, but TestLink is terrible with auth headers and session management. I wasted hours on this same integration before figuring out the real problem wasn’t endpoint availability - it’s how TestLink handles connection lifecycle. Even when everything looks configured right, TestLink constantly loses connection state between operations. You’ll get these random intermittent failures that are a nightmare to debug. The trial version handles XML-RPC calls fine, but TestLink’s implementation can’t deal with Jira’s security policies properly. You might get it working at first, then it’ll randomly stop syncing test cases or start creating duplicate issues. Don’t waste time fighting TestLink’s broken connector. Set up middleware instead that can handle proper sessions and retry logic when talking to Jira’s API.