Basic issue tracker interface

[m1ch13l]

Hi,

I've created a very basic issue tracker interface that is quick to set up and should work with most issue trackers that use numeric id's in the url to refer to a certain issue.
Downside is that there are no verification mechanisms included to check if an issue actually exists on the issue tracker system etc.
I've called it 'basicsoapinterface' since it is a very basic implementation of an issue tracker. It does not use any actual soap communication, but it seems an interface type must be provided to work correctly.

code is available on https://github.com/MichielVT/testlink-c ... pInterface

I'm not sure if it is worth adding it to the source because it has no verifications, but I thought I'd post it here as it may help other getting started with issue trackers that have no full integration yet.
I'm successfully using this with a SharePoint list used as issue tracker, but it should work with any web based service using numeric id's.

[fman]

Using SOAP in name when not true is not good.
what kind of interface are you using?

[m1ch13l]

Hi, I'm not using any API, it's just using an id number to generate the link.
Since I did not see a possibility to create a working interface without providing an API name, I picked a random existing one since I wasn't 100% sure if this value is restricted or used for some functions or checks.
I guess BasicHtmlInterface would be a more accurate name if that can be used?