https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292010-01-31T16:47:14ZRedmineRedmine - Feature #4702: Comment/close tickets from other projects' repository commit messageshttps://www.redmine.org/issues/4702?journal_id=139202010-01-31T16:47:14ZJean-Philippe Langjp_lang@yahoo.fr
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>Resolution</strong> set to <i>Duplicate</i></li></ul><p>Paul Adler wrote:</p>
<blockquote>
Just starting to use Redmine, I noticed two issues with my particular setup:
<ol>
<li>"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 <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Add option to make auto-fetch changesets fetch when activity/issues are viewed (New)" href="https://www.redmine.org/issues/1274">#1274</a> - basically the only place to learn about this behavior!?</li>
</ol>
</blockquote>
<p>This is described in the <a class="wiki-page" href="https://www.redmine.org/projects/redmine/wiki/FAQ#Commits-dont-show-up-in-the-activity-until-I-click-on-Repository">FAQ</a>.</p>
<blockquote>
<ol>
<li>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.</li>
</ol>
</blockquote>
<p>Fixed in <a class="changeset" title="Allow commits to reference issues of parent projects and subprojects (#4674)." href="https://www.redmine.org/projects/redmine/repository/svn/revisions/3357">r3357</a>, see <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: Sub-project repository commits not displayed on parent project issues (Closed)" href="https://www.redmine.org/issues/4674">#4674</a>.</p>