View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0010543 | mantisbt | relationships | public | 2009-05-27 08:37 | 2010-02-09 04:40 |
Reporter | oberger | Assigned To | |||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | acknowledged | Resolution | open | ||
Summary | 0010543: Proposal: Relationships to external bugs in remote bugtrackers | ||||
Description | We propose to add to mantis a plug-in which could help managing relationships between bugs in a Mantis instance, and external bugs in remote bugtrackers (not necessarily mantis) | ||||
Additional Information | Will be described in the wiki (link to be added later) | ||||
Tags | bts_link | ||||
Attached Files | |||||
We'd be delighted to Create a new dokuwiki page, but currently can't (insufficient privileges ?) In the meantime, here's what was drafted internally : https://picoforge.int-evry.fr/cgi-bin/twiki/view/Helios_wp3/Web/MantisMonitoringRemoteBugs Should someone please copy that to http://www.mantisbt.org/bugs/wiki.php?id=10543 so that all can amend the proposal ? |
|
I haven't reviewed the drafted requirements yet, but I've created a wiki page for this issue. You should have enough access to edit it. |
|
Thanks Victor. |
|
FYI, http://www.mantisbt.org/bugs/wiki.php?id=10543 is ready for review... feel free to comment here or in the wiki page. |
|
See also some related discussions initially sent on the ML : http://sourceforge.net/mailarchive/message.php?msg_name=1242031642.10766.1.camel%40erty.int-evry.fr |
|
oberger, sorry if I've missed this, but is the source code for the plugin (or whatever you used to make your screenshot) publicly available? If so, where at, and would you considering making it available on MantisForge? [1] Cheers |
|
This is a great idea. I've read through your proposal on the Wiki and have some comments and discussion to add.
|
|
Also in terms of architecture, you should check out the source-integration plugin at git.mantisforge.org for a good example of how to use plugins. I was thinking that each remote bug tracker type would need its own plugin (mantis, launchpad, bugzilla, trac, etc) to handle the communication and interface with the remote tracker. |
|
jreese, please find here the link to our on-going work: http://git.mantisforge.org/w/mantisbt/helios.git?a=shortlog;h=refs/heads/ext_plugin |
|
dhx, thanks for your comments and suggestions. Currently, we are trying to keep the external relationship similar to, but separate from, the in-built mantis relationships. However, it is true that making it viewable along with the other bug information, requires a certain amount of modification. We await the response of others in the mantis community to see their view. Our work has been added to the mantis git repository and the link provided in my previous post. The initial version of our feature will have a link to the external bug whose status would be tracked by an external agent, bts-link, in this case. There would be some functionality provided like, automatic closing of a local bug when its corresponding external bugs are closed. We are not looking at customised settings and behaviour for each remote tracker for the first version. Nothing will be pushed to remote trackers. Bts-link, running on the local mantis, will poll the remote trackers and update the changes in the local one. Regarding logging agent events, we will look into whether to keep previous change information or not. Like you said, as the information is already available, we might drop the idea. As for the polling of remote bugtrackers, things have to be finalised still. There might be a special status for bugs tracking security flaws, which will have their corresponding external bugs' tracked asynchronously. |
|
FYI, a similar feature (although less advanced ;) has been implemented in bugzilla 3.4, apparently : http://www.bugzilla.org/releases/3.4/release-notes.html#v34_feat_see |
|