Project

General

Profile

Actions

Feature #2120

closed

Different views between develop and funcional

Added by Andrea Maleci over 15 years ago. Updated 22 days ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
SCM
Target version:
-
Start date:
2008-10-31
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed

Description

Using Redmine I have problems linking with SCM (Subversion), because:

  • I have multiple projects on Redmine
  • Each project uses more than one SCM component (library, fron-end, back-end, authentication, etc..), with some of them shared between projects.
  • I can link only one SCM repository to a project.

Doing this I have done high-level project, one for macro-area, using subproject for real project.
My intent was to link macro-area to SCM repository, hoping that subproject inherit their parent SCM.

It seems not to be a good idea.

I've changed ./app/models/changeset.rb, and with this patch I can see now the revision link on my Issue:

***************
*** 83,88 ****
--- 88,99 ----
        action = match[0]
        target_issue_ids = match[1].scan(/\d+/)
        target_issues = repository.project.issues.find_all_by_id(target_issue_ids)
+
+       #Ora i child
+       Project.find(:all, :conditions => ["parent_id = ?", repository.project.id]).each { |cp|
+       target_issues = target_issues + cp.issues.find_all_by_id(target_issue_ids)
+      }
+
        if fix_status && fix_keywords.include?(action.downcase)
          # update status of issues
          logger.debug "Issues fixed by changeset #{self.revision}: #{issue_ids.join(', ')}." if logger && logger.debug?

Now if I click on revision number I get a 404 error, not found, instead of see changes on my code.
I suppose that someone else have the same problem, matching funcional view with project (and developement) view.
Any idea on how to resolve my error ?
Does someone has a better idea on how to review my project ?

Thanks a lot,
Andrea


Related issues

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

Actions
Related to Redmine - Feature #5386: Branch/Tags in Changeset DescriptionNew2010-04-27

Actions
Related to Redmine - Defect #7984: Confusing revisions links on repository rootNewToshi MARUYAMA2011-03-24

Actions
Related to Redmine - Feature #7246: Handle "named branch" for mercurialClosedToshi MARUYAMA2011-01-07

Actions
Actions #1

Updated by Holger Just 22 days ago

  • Status changed from New to Closed
  • Resolution set to Fixed

Fir quite some time, you can

  • have multiple repositories per project (#779)
  • link to issues in any project (#3087)

As such, I believe your patch is not necessary anymore and your requirements can all be met with basic Redmine.

Actions

Also available in: Atom PDF