User Tools

Site Tools


mantisbt:issue:10543

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
mantisbt:issue:10543 [2009/05/28 09:01]
oberger Ready for review
mantisbt:issue:10543 [2009/07/03 11:09] (current)
mdhar
Line 12: Line 12:
   * provide a formal way to describe pointers to other //external bugs// in remote bugtrackers, set by and displayed for the persons interested in the bugs (more formal than URLs added in notes, since a //semantics// is defined for types of relations).   * provide a formal way to describe pointers to other //external bugs// in remote bugtrackers, set by and displayed for the persons interested in the bugs (more formal than URLs added in notes, since a //semantics// is defined for types of relations).
   * allow the use of such relations by //agents// which could automatically //monitor// such external bugs. A first use could be to notify these interested persons whenever a //status change// of the remote bug is noticed by agents, as is done by //bts-link// for the debbugs Debian bugtracker (or similar features).    * allow the use of such relations by //agents// which could automatically //monitor// such external bugs. A first use could be to notify these interested persons whenever a //status change// of the remote bug is noticed by agents, as is done by //bts-link// for the debbugs Debian bugtracker (or similar features). 
 +
  
 ===== Bug relationships ===== ===== Bug relationships =====
Line 17: Line 18:
 Mantis already provides certain relationship_types in the "metadata", for property of relations between bugs. Currently however, this feature is only for linking local bugs (in the same mantis instance). Through the plugin, we propose to add additional relationship_types and also allow the current relationship_types for external bugs (also called remote bugs / external bugs ?). The new relationship_types could represent different semantics, like: Mantis already provides certain relationship_types in the "metadata", for property of relations between bugs. Currently however, this feature is only for linking local bugs (in the same mantis instance). Through the plugin, we propose to add additional relationship_types and also allow the current relationship_types for external bugs (also called remote bugs / external bugs ?). The new relationship_types could represent different semantics, like:
   * "See also" : meant for general URL pointing to other bugs without further semantics   * "See also" : meant for general URL pointing to other bugs without further semantics
-  * "Forwarded upstream" : meant for distributions monitoring upstream projects for instance (and used by agents like bts-link) +  * "Forwarded upstream" : meant for distributions monitoring upstream projects for instance (and used by agents like bts-link) 
 +  * "External Duplicate of" : meant for duplicate bugs in other projects
  
 In addition, the current relationship types used for local bugs could also be used for external bugs (parent / child, etc.) It will be the administrator's duty to define the relationship types in an understandable way, and compatible with the agents capabilities (see below). In addition, the current relationship types used for local bugs could also be used for external bugs (parent / child, etc.) It will be the administrator's duty to define the relationship types in an understandable way, and compatible with the agents capabilities (see below).
Line 40: Line 42:
  
 The log would be available as RSS too. The log would be available as RSS too.
 +
  
 ===== Needs for bts-link ===== ===== Needs for bts-link =====
  
  
-As per the need of bts-link, the plugin would monitor specifically "forwarded-upstream" relations meaning that the bug is no longer local but needs to be addressed in an external bugtracker. Additional "resolution" values would be added to the existing ones :+As per the need of [[http://bts-link.alioth.debian.org/|bts-link]], the plugin would monitor specifically "forwarded-upstream" relations meaning that the bug is no longer local but needs to be addressed in an external bugtracker. Additional "resolution" values would be added to the existing ones :
   * fixed-upstream   * fixed-upstream
   * reopened-upstream    * reopened-upstream 
Line 57: Line 60:
  
 //Note : the following proposal is made in the frame of the [[https://picoforge.int-evry.fr/cgi-bin/twiki/view/Helios_wp3/Web/|Helios]] project working on the subject of bugtracker synchronisation.// //Note : the following proposal is made in the frame of the [[https://picoforge.int-evry.fr/cgi-bin/twiki/view/Helios_wp3/Web/|Helios]] project working on the subject of bugtracker synchronisation.//
 +
 +Note that in waiting for this feature to be integrated in Mantis, we have devised a working version of bts-link anyway, see : http://permalink.gmane.org/gmane.comp.bug-tracking.mantis.devel/2457 
  
mantisbt/issue/10543.1243515713.txt.gz · Last modified: 2009/05/28 09:09 (external edit)