Feature #5835
closed
Allow links to other project's changesets
0%
Description
It would be nice to qualify the project of a link e.g. project-id:r20 to link to changeset 20 of project-id. This is especially useful for subprojects. Right now there doesn't seem to be a clean way to link to a subproject's changeset from its parent.
Related issues
Updated by Holger Just almost 14 years ago
- Subject changed from Qualifying links to Allow links to other project's changesets
- Category set to Text formatting
Updated by Henrik Ammer over 13 years ago
Also this is needed when someone commit to the repo with a text that should close or refer a ticket but the ticket is in a subproject of the project that has the repo.
Confused?
- Project 1 - Has the repo
- Subproject 1 - Has the ticket that should be closed/refered
Better now? :)
Updated by Mischa The Evil over 13 years ago
Henrik Jönsson wrote:
Also this is needed when someone commit to the repo with a text that should close or refer a ticket but the ticket is in a subproject of the project that has the repo.
Confused?
- Project 1 - Has the repo
- Subproject 1 - Has the ticket that should be closed/refered
Better now? :)
Henrik, am I right when I say that this specific case is already fixed/implemented by Jean-Philippe with r3357 for issue #4674?
Updated by Mischa The Evil about 3 years ago
- Status changed from New to Closed
- Resolution set to Fixed
Jim Naslund wrote:
It would be nice to qualify the project of a link e.g. project-id:r20 to link to changeset 20 of project-id. [...]
This was actually implemented for issue #7409 with the following syntax:
sandbox:r758 (link to a changeset of another project with identifier "sandbox") sandbox:commit:c6f4d0fd (link to a changeset with a non-numeric hash of another project with identifier "sandbox")
Closing as such. Please re-open if needed.
Updated by Mischa The Evil about 3 years ago
- Related to Feature #7409: Cross project Redmine links added