I had to change the bug field from an integer to a varchar field.
Once I did that I could properly link my defects. (EXT-1, etc)
Search found 5 matches
- Fri Dec 01, 2006 7:56 pm
- Forum: TestLink 1.6 (closed)
- Topic: Connecting Testlink with Jira
- Replies: 5
- Views: 12298
- Fri Dec 01, 2006 7:55 pm
- Forum: TestLink 1.6 (closed)
- Topic: TestLink 1.6 and Jira 3.5.3
- Replies: 4
- Views: 7391
- Fri Dec 01, 2006 7:25 pm
- Forum: TestLink 1.6 (closed)
- Topic: TestLink 1.6 and Jira 3.5.3
- Replies: 4
- Views: 7391
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 tab...
- Fri Dec 01, 2006 7:09 pm
- Forum: TestLink 1.6 (closed)
- Topic: TestLink 1.6 and Jira 3.5.3
- Replies: 4
- Views: 7391
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 ...
- Fri Dec 01, 2006 7:03 pm
- Forum: TestLink 1.6 (closed)
- Topic: Connecting Testlink with Jira
- Replies: 5
- Views: 12298
I just hooked up Jira 3.6.5 with TestLink 1.6.2. I followed the directions, but the one item I ran into was that it seems this version appends a product key to the defects in both the DB and URL. E.g. http:/.../jira/browse/(Abbrev.)-(Defect ID) This also happens in the database when checking the ite...