Jira and testlink integration for complex project

[venn]

I saw in several posts info about TestLink support the SOAP integration with Jira in mode project-to-project.
The baseline is "You need to create an ISSUE TRACKED DEFINITION that point TO EACH Mantis project where you want to be able to report the issue.
ONE TestLink TestProject can have ONLY ONE Issue Tracker definition and ONE issue tracker definition can ACT ONLY ON ONE BTS project."
My vision:
1. User has to create one project in BTS(JIRA) and one project in TestLink
2. User has to add one Issue Tracker in Issue Tracker Management
3. User has to assign issue tracker from step 2 to specified project in Testlink
The result is ability to create or link issues from test execution.

But what should I do in case of complex regression tests for multimodule application. It means we can organise several projects in Jira( N app modules and N+M projects in Jira) and want to create one project in TestLink to full regression tests execution for whole application.
Now I can configure issue tracker on one specific project in Jira(section projectkey), but I have had the ability to link existing in Jira issues from another projects to test execition for this testlink project still.
In addition. I can do this but with messages about issue tracker configuration catching at the top of sections.
For example:
"оbject(SimpleXMLElement)#148 (8) { ["username"]=> string(8) "ХХХХ" ["password"]=> string(10) "ХХХХ" ["uribase"]=> string(24) "ХХХХХХ" ["uriwsdl"]=> string(56) "ХХХХ" ["uriview"]=> string(31) "ХХХХХХ" ["uricreate"]=> string(56) "ХХХХ" ["projectkey"]=> string(4) "ХХХ" ["issuetype"]=> string(1) "1" }"

Could anybody from Testlink guru approve/add more info about integration basic logic for now and the nearest future?
Could that guys explane any appropriate rules for test building for my case?

[fman]

1. when you get weird things on GUI is time to do some search first on mantis, then on forum
the printout you see is debug info that was not removed (already reported on Mantis and on forum)

2. when We talk of ONE ISSUE TRACKER for EACH JIRA project, this apply if you want to create issues directly from testlink, because projectkey is ONLY USED in this context.
You can link existent ISSUES from multiple JIRA projects

[venn]

Thanks for your advices!

[yueran]

So right now 'ONE ISSUE TRACKER for EACH JIRA project' means that if I want to create jira ticket directly from testlink, I have to create one issue tracker for each JIRA project?

Is there a way that I can configure one issue tracker from testLink, for all the test projects? which means one issue tracker contains multiple projectkey, that when creating jira ticket from testLink, I could select a project from the project list?

Thank you!