I can link existing Jira issues to TestLink without any issues. However, when I try to create a new issue, the Version field doesn’t accept any input or show any options, as indicated in the image below. I’ve attempted to create versions in Jira but it hasn’t resolved the problem.
Here are a few questions I have:
What should I enter in the Version field when I’m creating an issue?
What does <issuetype>1</issuetype> refer to, and can it be replaced with another value?
How can I add more fields to the create issue interface?
The label “Version” in TestLink seems to differ from the label “Versions” in Jira. What’s the cause of this mismatch?
Any assistance would be much appreciated since I’m currently stuck with this integration.
The version dropdown breaks because TestLink’s API times out when grabbing Jira project versions. I’ve seen this with bigger Jira instances - the version list just takes too long to load. Your XML config looks fine, but try adding a timeout parameter if your TestLink version supports it. For issuetype values, those are Jira’s internal issue type IDs. Go to your Jira project settings and check the network tab when issue types load - you’ll see the actual numeric IDs in the REST responses. Here’s what worked for me: create a separate Jira project just for TestLink integration with fewer versions and simpler workflows. This speeds up API responses and makes the version field load consistently. Also double-check that your TestLink user has the right Jira permissions - sometimes field visibility problems look like integration issues. The “Version” vs “Versions” label thing is hardcoded in TestLink’s language files, so you’re stuck with that.
Had the same headache with this integration last year. The version field breaks because of how TestLink hits Jira’s API for versions. Check that your Jira versions are released or unreleased - not archived. TestLink completely ignores archived versions.
For the issuetype parameter, you need your Jira instance’s actual issue type IDs. Go to Administration > Issues > Issue types and hover over each edit link. The ID shows up in the URL. Bug’s usually 1, but every Jira setup’s different.
Field mapping is TestLink’s worst part here. They built it for basic stuff only. Want more? You’re editing TestLink’s source code - the issuetracker classes specifically. Don’t do it unless you know PHP well.
Here’s what worked for me: create a custom Jira screen scheme just for TestLink issues. Strip it down to essential fields only. Won’t fix TestLink’s interface, but makes issue creation way smoother.
Been down this exact rabbit hole before. TestLink’s native Jira integration is honestly a pain to work with.
For your questions:
Version field needs to match exact version names from your Jira project. Check Project Settings > Versions in Jira.
issuetype 1 is usually “Bug” - you can find the right numbers in Jira’s issue type scheme settings.
Adding more fields requires custom TestLink code modifications. Not fun.
The label mismatch happens because TestLink hardcodes field names poorly.
Here’s what I actually did when I faced this mess: ditched the native integration completely and built a proper automation workflow with Latenode.
Set up webhooks from TestLink to catch test failures, then automatically create Jira issues with all the fields you want. No XML config headaches. No missing dropdowns. You can map any TestLink data to any Jira field exactly how you need it.
Plus you get proper error handling and can add stuff like automatic assignee rules based on test categories or component mapping.
Takes maybe an hour to set up vs days of fighting with TestLink’s built-in limitations.