mantisbt:issue:10543
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
mantisbt:issue:10543 [2009/05/27 12:53] – created vboctor | mantisbt:issue:10543 [2009/07/03 11:09] (current) – mdhar | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | TBD | + | ====== Proposal : Provide an extension adding Relationships to external bugs in remote bugtrackers ====== |
+ | |||
+ | **Authors** : | ||
+ | * Olivier Berger < | ||
+ | * Madhumita Dhar | ||
+ | |||
+ | //This proposal has been added here for review by Mantis devs, accompanying http:// | ||
+ | |||
+ | **We propose to have a plugin in Mantis which facilitates the monitoring of remote-bugs.** | ||
+ | |||
+ | There are 2 goals for this extension of Mantis : | ||
+ | * provide a formal way to describe pointers to other //external bugs// in remote bugtrackers, | ||
+ | * 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 // | ||
+ | |||
+ | |||
+ | ===== Bug relationships ===== | ||
+ | |||
+ | Mantis already provides certain relationship_types in the " | ||
+ | * "See also" : meant for general URL pointing to other bugs without further semantics | ||
+ | * " | ||
+ | * " | ||
+ | |||
+ | 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' | ||
+ | |||
+ | ==== Description of the data ==== | ||
+ | |||
+ | Each local bug is permitted to have multiple relationships which connect it to different external bugs. Each of these relations would have: | ||
+ | * a bug_id (local) | ||
+ | * a URL of the external bug (could be split in remote bugtracker URL + ID in that bugtracker) * (optional) an external " | ||
+ | * a relation_type among the ones configured globally (see bellow) | ||
+ | * a log corresponding to the state changes of the remote bug over time as monitored by an agents, bts-link, for e.g. (during each periodic run, the agent appends to the log if there is a status change). The log contains a lists of entries : | ||
+ | * the agent login | ||
+ | * the date of addition | ||
+ | * the status and other properties of the remote bug noticed at the time of processing (potentially formatted in a suitable way for agents to retrieve) | ||
+ | * the login of the agent authorized to append to that log if set. If unset, the first agent to " | ||
+ | |||
+ | There is a set of configured external_bugs_relation_types with : | ||
+ | * a " | ||
+ | * a " | ||
+ | |||
+ | Whenever new elements are added to the external bug's log, notifications are sent by mantis to all users who have the monitoring property On for its local bug. These notifications are sent in the same way through emails, as is done for comments added to the bug, for all those monitoring it, reporter, etc. | ||
+ | |||
+ | The log would be available as RSS too. | ||
+ | |||
+ | |||
+ | ===== Needs for bts-link ===== | ||
+ | |||
+ | |||
+ | As per the need of [[http:// | ||
+ | * fixed-upstream | ||
+ | * reopened-upstream | ||
+ | |||
+ | These could be set by the bts-link agent, in addition to its additions to the relationship logs, to allow reports to be performed on such " | ||
+ | |||
+ | The agent will fetch (through soap) a list of all bugs whose external bugs are to be monitored by bts-link (filtering by relation_ship types). This would consist of the local bug ids and the corresponding external bug URLs. By default only open bugs will be returned, but an option could be used to retrieve closed ones as well. | ||
+ | |||
+ | Whenever a related external bug is closed as a duplicate of another one, the one still open will be saved and proposed instead of the one recorded initially. | ||
+ | |||
+ | The bts-link allowed to monitor a relation_type on a mantis instance will extract the previous state from the most recent entry notifying the status in its log. In case concurrent tools are running, the others will not use that log nor notify users through mantis, but they could run nevertheless, | ||
+ | |||
+ | //Note : the following proposal is made in the frame of the [[https:// | ||
+ | |||
+ | Note that in waiting for this feature to be integrated in Mantis, we have devised a working version of bts-link anyway, see : http:// |
mantisbt/issue/10543.1243443214.txt.gz · Last modified: 2009/05/28 08:57 (external edit)