Actions
Feature #4702
closed
Comment/close tickets from other projects' repository commit messages
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
SCM
Target version:
-
Start date:
2010-01-31
Due date:
% Done:
0%
Estimated time:
Resolution:
Duplicate
Description
Just starting to use Redmine, I noticed two issues with my particular setup:
- "refs #123" and "closes #123" in a commit message don't trigger the intended actions before the repository is visited. This is unfortunate and already noted in #1274 - basically the only place to learn about this behavior!?
- It is obviously not possible to comment/close a ticket that belongs to a different project. 'Different' means that the changeset with the commit message goes to a repository associated with a project different from that where the ticket was filed against.
I use a "master project" with several subprojects to have a common ticket space. Problems are solved in several subprojects that each have a mercurial repository associated. The idea is to have a developer use a commit message to trigger an action for a ticket filed against the "master project".
Related issues
Updated by Jean-Philippe Lang almost 15 years ago
- Status changed from New to Closed
- Resolution set to Duplicate
Paul Adler wrote:
Just starting to use Redmine, I noticed two issues with my particular setup:
- "refs #123" and "closes #123" in a commit message don't trigger the intended actions before the repository is visited. This is unfortunate and already noted in #1274 - basically the only place to learn about this behavior!?
This is described in the FAQ.
- It is obviously not possible to comment/close a ticket that belongs to a different project. 'Different' means that the changeset with the commit message goes to a repository associated with a project different from that where the ticket was filed against.
Actions