Project

General

Profile

Actions

Defect #6857

open

git references leaking from subproject to project

Added by Bernhard Furtmueller over 13 years ago. Updated over 10 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
SCM
Start date:
2010-11-09
Due date:
% Done:

0%

Estimated time:
Resolution:
Affected version:

Description

Since redmine can't share repositories to subprojects yet we added the repository twice (to project and subproject).

Now trackers which are referenced in the repository get commit messages attached twice. One time from the project's repo and one time from the subproject's repo.

I'd consider this leaking a bug (or a first step to shared repos ;) )


Related issues

Related to Redmine - Feature #1657: Subprojects can share their parent project's repositoryNew2008-07-17

Actions
Related to Redmine - Patch #2144: Patch for main-level repositoryClosedJean-Philippe Lang2008-11-072008-11-07

Actions
Related to Redmine - Patch #2256: Allow commit messages to refer to issues in project ancestor tree, not just projectClosed2008-12-01

Actions
Related to Redmine - Feature #3687: Possibility to link all projects to a single SVN repositoryNew2009-07-29

Actions
Related to Redmine - Patch #9359: invert project <-> repository relationshipNew2011-09-30

Actions
Has duplicate Redmine - Defect #8225: Revisions that reference issues are duplicated if their repository is listed for a project and its subprojectsNew2011-04-26

Actions
Has duplicate Redmine - Defect #5126: Associated revision shown multiple timesClosed2010-03-19

Actions
Has duplicate Redmine - Defect #32191: Duplicate associated revisions when using multiple repositories for a projectNew

Actions
Actions #1

Updated by Bernhard Furtmueller over 13 years ago

I think there were already some attempts getting the root problem (sharing repos) fixed or asked.

Feature #1657 Subprojects can share their parent project's repository
Patch #2144 Patch for main-level repository
Patch #2256 Allow commit messages to refer to issues in project ancestor tree, not just project

Actions #2

Updated by Etienne Massip over 12 years ago

  • Target version set to Candidate for next minor release

Yet to be confirmed.

Actions #3

Updated by Mischa The Evil over 12 years ago

Etienne Massip wrote:

Yet to be confirmed.

I haven't looked into this issue deeply but considering r3357 for issue #4674, which was included first in Redmine 0.9.2, it looks like it is logical behavior.

Actions #4

Updated by Fernando Hartmann over 11 years ago

+1
This happens to me too

Actions #5

Updated by Ivan Cenov about 11 years ago

This happens in 2.2.3.stable too with Subversion repositories.

Actions #6

Updated by Jethro Yu almost 11 years ago

This happens in 2.2.3.stable too with git repositories.

Actions #7

Updated by Ralph Twele over 10 years ago

I have this happening with 2.3.0. It is not only related to parent-child Projects. I have one repository containing a document describing general development rules. This is included in many Redmine projects. If I commit a change to the document referencing a ticket the new revision will be listed in the ticket multiple times.

Actions #8

Updated by Go MAEDA about 8 years ago

  • Has duplicate Defect #5126: Associated revision shown multiple times added
Actions #9

Updated by Go MAEDA over 4 years ago

  • Has duplicate Defect #32191: Duplicate associated revisions when using multiple repositories for a project added
Actions

Also available in: Atom PDF