Opened 20 years ago
Closed 19 years ago
#688 closed defect (duplicate)
Cross-project linking
| Reported by: | anonymous | Owned by: | Jonas Borgström |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | general | Version: | 0.7.1 |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
It would be great if there was a way to link from one Trac instance to another. This can be accomplished by having a config file on a machine with all Trac instances and their names. The link format can be something like 'TRACLINK:<instance name>:<identifier>', where <identifier> would be anything that is legal to link to in Trac.
This is far simpler then a full-blown multi-project management, but it would solve vast majority of cross-project issues. The case I am thinking of (and actually have to deal with today) is that there is a common base library and several independent projects that use it. There is never [very rarely] a case of content (tickets/wiki/etc) moving from one instance of Trac to another. But when working with the base library there is a frequent need to reference something in one of the other projects (e.g. a feature/bug in a project requires some work in the base library - it would be ideal to create a ticket in the base library Trac with a link to the discussion of that issue in the original project's Trac).
Attachments (0)
Change History (3)
comment:1 by , 20 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
comment:2 by , 19 years ago
| Resolution: | wontfix |
|---|---|
| Status: | closed → reopened |
Actually, this ticket describes nicely the need for InterTrac links.
comment:3 by , 19 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | reopened → closed |
… and as such, its more a duplicate of #234.
Support for interwiki links is more generic, simpler, and probably alot more useful.
See #40.