Patch #24434

Link Redmine Issues to Mercurial Branch name

Added by Ewan Makepeace almost 6 years ago. Updated almost 6 years ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:


Target version:-


In our company we start a new Mercurial branch for every feature request. Our branch naming looks like "RM1234" where 1234 is the issue concerned.

Rather rely on issue numbers embedded in commit messages which relies on developer discipline and I find is not always relable we made the attached patch to take the issue number directly from the branch name.

I hope this may be of interest to others.

  1. It is unfortunate that Reedmen does not feature branch names anywhere. Neither in the summary of change sets on the issue page nor even on the changes detail page is the name of the branch specified. For us this is highly desirable (much more so than the changes ID).
  2. I could see no Category in this Redmine related to Version Control, Repository support or Mercurial but am assuming SCM is the correct category?

redmine-mercurial.patch Magnifier (2.61 KB) Ewan Makepeace, 2016-11-23 05:21


#1 Updated by Ewan Makepeace almost 6 years ago

Note: We have used this patch on versions 2.5.2 and 2.6.1 but not tested elsewhere.

#2 Updated by Toshi MARUYAMA almost 6 years ago

Could you move Mercurial specific code to derived model (e.g. Repository::Mercurial)?

Also available in: Atom PDF