Defect #7593
closed
Git: Associated revisions in issue view doesn't use the Referencing keywords
0%
Description
Hello,
in Redmine 1.10 and 1.11 I found that using GIT as SCM
the linking of commits and the Issue using " keyword #123 " only
works for keyword refs (eg. ref #234) , but not for others, e.g. IssueID or any self defined keywords.
Only when writing refs # 123 in "Associated revisions" in the issue #123 the commit is listed.
Is it a question of a redmine setting or is it a real bug?
Files
Updated by Matthias Neubert almost 14 years ago
I guess it is a bug. Can someone confirm that this is the case (at least using a git repository)
btw. : I forgot to set cathegory SCM and now I cannot change anymore
Updated by Toshi MARUYAMA almost 14 years ago
- Subject changed from Associated revisions in issue view doesn't use the Referencing keywords to Git: Associated revisions in issue view doesn't use the Referencing keywords
Git has 7 days problem #7146.
Updated by Matthias Neubert almost 14 years ago
Its not the 7 days Problem. Also we don't have problems gettings references to commits in not-master branches.
As long as we use "refs" in commit message everything works fine.
But "IssueID" an every other keyword does not work.
btw: when in repository view the #12345 is linked correctly to the issue 12345 in the commit messages.
The problem is the way back: listing commits in issue view by using other keywords than refs or even none (which would be best for me) using the special Keyword IssueID.
Used components:
Git 1.7.3.1
Redmine 1.1.0
MySQL
Updated by Toshi MARUYAMA almost 14 years ago
- File setting.png setting.png added
- File hg-repo.png hg-repo.png added
- File issue.png issue.png added
It works fine on my Mercurial test repository.
Updated by Toshi MARUYAMA almost 14 years ago
- Status changed from New to Closed
- Resolution set to Invalid
You can use '*' in setting.
For example.
https://www.chiliproject.org/issues/170
Updated by Matthias Neubert almost 14 years ago
Hello,
is it possible that changing the reference keyword (e.g. to * , which I already tried)
only affects new commits, which happen after setting the keyword to * ?
Is there a rake command to run refresh all these tickets to use the new * as reference key?
regards
Matthias
Updated by Matthias Neubert almost 14 years ago
I ll try this as an workarround:
"I had to delete the repository from the project and re-add it to get the associations updated."