Hello!
I am in the process of selecting a test management tool. We need an open source tool that will interface with Jira, so TestLink seems to be a perfect solution.
I read in the TestLink 1.6 Installation and Configuration Manual that the supported version of Jira is 3.1.1. We have Jira version 3.5.3 and would like to set up an interface with TestLink.
Has anyone tried or successfully interfaced TestLink with Jira version 3.5.3?
Thanks!
TestLink 1.6 and Jira 3.5.3
I just did it here in a few minutes.
There is a few problems. It seems that 3.5.3 now prepends all Defect ID's with the Project Key associated to that defect.
This means that the database queries to check status and and the URL don't work quite right.
If you only have 1 project, it is quite easy to edit the php code to fix the query (just hardcode the project key) but it looks like it will be a lot more work to get it to scale across multiple projects.
It would make some sense to patch in the ability to make the bug ID a text field to support the 3 character key + ID. That may be the easiest way to fix it.
There is a few problems. It seems that 3.5.3 now prepends all Defect ID's with the Project Key associated to that defect.
This means that the database queries to check status and and the URL don't work quite right.
If you only have 1 project, it is quite easy to edit the php code to fix the query (just hardcode the project key) but it looks like it will be a lot more work to get it to scale across multiple projects.
It would make some sense to patch in the ability to make the bug ID a text field to support the 3 character key + ID. That may be the easiest way to fix it.
So, I just quickly did the following and it seems everything is working perfectly.
Changed the type of field 'bug' in table 'bugs' from int to varchar(10). This allows me to specify bugs in the format 'XXX-1' for example, which would map to Jira 3.5.3 Project XXX bug 1.
The SQL I used was:
alter table bugs modify column bug varchar(10);
No other changes are required, it is pulling and mapping statuses fantastically.
I'll post back if I find any problems doing some more testing.
Your mileage may vary, use at your own risk, etc... ofcourse.
Changed the type of field 'bug' in table 'bugs' from int to varchar(10). This allows me to specify bugs in the format 'XXX-1' for example, which would map to Jira 3.5.3 Project XXX bug 1.
The SQL I used was:
alter table bugs modify column bug varchar(10);
No other changes are required, it is pulling and mapping statuses fantastically.
I'll post back if I find any problems doing some more testing.
Your mileage may vary, use at your own risk, etc... ofcourse.