Read-only milestone linking to external trac projects

[posix # inmail24 | com]

It may be useful for different groups (with different trac projects) that are dependent or need awareness of the progress of other trac projects, to interlink specific trac milestones outside their own particular trac project.

Not sure of the workload required for functionality.

[Christian Boos]

Some basic support can be obtained by the use of InterTrac links.

For example, say you have project A depending on some project B milestones (called RELEASE_1, RELEASE_2, etc.)

If you want to link to them in project A, here are some options:

in 0.10dev

In project A, you can create "proxy" milestones, B/RELEASE_1, B/RELEASE_2, etc.

Each of these proxy milestones will have a description containing an intertrac link: e.g. Remote milestone b:milestone:RELEASE_1.

using WorkFlow branch

In project A, you can create a custom text field related_milestone which can directly be filled with an intertrac link to the b:milestone:RELEASE_1.

NB: In the WorkFlow branch, all text fields are implicitely wiki texts, unless explicitely configured with .plaintext = true.

[Christian Boos]

Besides the suggestions given above, 1.0 will provides true multi-project support, and it will then be possible to look at a combined roadmap.

[Christian Boos]

Milestone 1.0 deleted