|Anonymous | Login | Signup for a new account||2018-12-14 11:28 UTC|
|Main | My View | View Issues | Change Log | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001878||TestLink||New Feature||public||2008-11-18 03:51||2013-05-20 19:33|
|Product Version||1.8 RC 1|
|Fixed in Version||1.9.5 (2012 Q4 - bug fixing)|
|Summary||0001878: BTS - Support for multiple BTS per installation|
|Description||We are currently migrating from one BTS (Bugzilla) to another (JIRA). At the present time, Testlink only supports the definition for a single adapter which is available across the board.|
It would be very useful to be able to define more than one adapter and be able to select which adapter to use when creating a project. hence we could have a project using BugZilla while another one could be using Jira.
This is a model used by redmine for instance for repositories.
|Additional Information||Furthermore, it would be even better to be able to select the adapter on a per occurrence basis. For example, our projects are being re-used across multiple versions our product live cycle. There might be a need from other people for such feature (we have over 9000 test cases and such migration is difficult).|
P.S.: Great job on 1.8. The Test Specification Tree refresh went from 45 seconds to less than 3.
|Tags||No tags attached.|
|QA Team - Task Workflow Status||READY FOR TESTING|
>> Furthermore, it would be even better to be able to select the adapter on a per occurrence basis
Explain better please
Basically, be able to select the adapter to use rather then the default (optional). For instance, let say we have 2 adapters (Bugzilla, JIRA) then someone could assign a bug from either one database.
I work for a semi conductor company. We have to deal with VLSI and software, often time working off different bug tracking system.
I hope this clarifies things. This is really icing on the cake. But on a per project basis would be great.
Yes I think it may be useful, but i believe (as you've stated) a per project basis should be sufficient.
In my opinion a 1:1 relationship of project to bugtracking makes sense
1:n seems overkill (-:
You are right. After thinking about it, I think 1:1 is fine. We have very long lived projects and we will soon encounter a case where there will be a transition (i.e. one version on bugzilla and the new one on Mantis) but we will just have to bite the bullet.
Thanks again for this great system. So far 1.8 RC1 has been working pretty well for us.
Yes. It makes sense for me too.
So there could be a new parameter for test project, that define used tracker. Admin can choose it via GUI.
Configuration file should define which tracker are allowed.
Believe it or not we now have an 1:n relationship. Basically, we maintain two bug database (one internal and one external for our customers). Also, our products have dependencies on sub-system which use different databases.
So here is a real use case. But obviously a 1:1 relationship will work fine as well (We currently tie the dependencies between bug databases in the databases themselves).
This feature would also be of vital interest for our company. We have hundreds of projects each of them having to deal with a different bug tracking system (Jira, SourceForgem, TeamForge, Bugzilla,...)
A 1:1 relation between project and BTS would be highly appreciated.
When is this planned?
There are no plans.
We can accept contribution is you are able to develop it.
|2008-11-18 03:51||Laurent||New Issue|
|2008-11-18 03:51||Laurent||Browser||=> N/A|
|2008-11-19 02:10||fman||Note Added: 0004643|
|2008-11-19 06:16||Laurent||Note Added: 0004644|
|2008-11-20 04:08||schlundus||Note Added: 0004661|
|2008-11-20 12:18||Laurent||Note Added: 0004670|
|2008-11-21 01:05||mhavlat||Note Added: 0004678|
|2008-11-21 01:05||mhavlat||Status||new => acknowledged|
|2008-11-27 03:03||schlundus||Severity||major => feature request|
|2009-08-30 02:58||Laurent||Note Added: 0007874|
|2010-11-04 10:00||volker.herren||Note Added: 0012270|
|2010-11-04 10:08||fman||Note Added: 0012271|
|2013-05-20 19:33||fman||QA Team - Task Workflow Status||=> READY FOR TESTING|
|2013-05-20 19:33||fman||Status||acknowledged => closed|
|2013-05-20 19:33||fman||Assigned To||=> fman|
|2013-05-20 19:33||fman||Resolution||open => fixed|
|2013-05-20 19:33||fman||Fixed in Version||=> 1.9.5 (2012 Q4 - bug fixing)|
|Copyright © 2000 - 2018 MantisBT Team|