Feature #5242
closedDisplay source project for cross-project associated revisions for issues
0%
Description
When an issue has an associated revision that is in a different project, display its source project as follows:
Revision 90 (in Website)
Added by Michael Ekstrand about 1 hour ago
Also, make the project name a link to an appropriate page in the project (either its summary or its issue list, I would think).
This will enable readers to quickly see that the associated revision is actually in a different project, something that is difficult at present.
Files
Related issues
Updated by Felix Schäfer over 14 years ago
- File adds_project_name_to_associated_revision_link.patch adds_project_name_to_associated_revision_link.patch added
This patch adds the name of the project to an associated revision if it's not the same as the current project.
Updated by Go MAEDA about 6 years ago
- Category changed from UI to SCM
- Target version set to Candidate for next major release
Updated by Yuichi HARADA almost 6 years ago
- File cross-project-associated-revisions.png cross-project-associated-revisions.png added
- File adds_project_name_to_associated_revision_link_v2.patch adds_project_name_to_associated_revision_link_v2.patch added
I rebuilt the patch to work with the latest Redmine.
In the cross-project it looks like the following.
Updated by Go MAEDA over 5 years ago
- Related to Feature #13715: show SCM identifier (repository) in associated revisions added
Updated by Go MAEDA almost 3 years ago
- File adds_project_name_to_associated_revision_link_v3.patch adds_project_name_to_associated_revision_link_v3.patch added
- Target version changed from Candidate for next major release to 5.0.0
Updated the patch for the current trunk (r21360).
Setting the target version to 5.0.0.
Updated by Go MAEDA almost 3 years ago
- File adds_project_name_to_associated_revision_link_v4.patch adds_project_name_to_associated_revision_link_v4.patch added
- File v4.png v4.png added
Updated the patch again. I think it is even better to show the project name using the format "Project - Revision 999" rather than "Revision 999 (Project)".
- In the original patch, two "()" appear after the revision like this: "(Project) (diff)"
- The way the project name is displayed first is consistent with "Related issues" section
Updated by Go MAEDA almost 3 years ago
- Status changed from New to Closed
- Assignee set to Go MAEDA
- Resolution set to Fixed
Committed the patch. Thank you for your contribution.