Avoid multiple BT instances initialization

[okainov]

Description of problem

Connection to BT is being established every time when object-child of IssueTrackerType is being created. For JIRA specifically, it means that every time new jira.JIRA object is being created and new connection is being established. Taking into account possibility of multiple requests it makes sense to extract establishing the connection to some kind of singleton or classmethod.

Actually, from the first sight I would say that all methods from IssueTrackerType should be static, so calls should look like:
JIRA.add_testcase_to_issue(case, bug)

Component (web, API, etc)

core

Additional info

[okainov]

Simple partial solution which will already help if someone first gets IssueTracker object and than executes multiple requirests to it is just to declare rpc as Jira class variable and in init you add check if JIRA.rpc is not None

[atodorov]

Simple partial solution which will already help if someone first gets IssueTracker object and than executes multiple requirests to it is just to declare rpc as Jira class variable and in init you add check if JIRA.rpc is not None

For the record you will have to keep a reference to the tracker parameter b/c there could be multiple JIRA instances defined in the database. Making a rpc attribute class based will always point to the first instance that happens to be used by the engineer reporting a bug. The next person that wants to report a bug may be working on a completely different product.

[okainov]

I believe, multiple JIRA instances is kind of exceptional case. We implemented this WA in our fork and pretty happy with it. But of course there is always space for improvements