Project

General

Profile

Commit Appears in Repository Tab but Not Linked to Issue Until Manually Visited

Added by D K about 2 months ago

Hello,

I've encountered an issue with Redmine where commits are correctly showing up under the "Repository" tab but are not automatically linked to the related issue in the "Associated revisions" section of the issue page. This link only seems to be established after I manually visit the "Repository" tab; only then does the commit appear in the issue's "Associated revisions."

Here's the sequence of events:

I commit changes to the repository with a message that references an issue (e.g., "Fixes #1234 - corrected typo").
The commit immediately appears under the "Repository" tab, indicating that Redmine successfully fetches the commit.
However, when I navigate to the referenced issue #1234, the "Associated revisions" section does not display the new commit.
It is only after I visit the "Repository" tab and then return to the issue page that the commit appears in the "Associated revisions."
This behavior requires an unnecessary step to link commits to issues, which is not ideal for tracking changes and updates efficiently. Is there a way to ensure that commits are automatically linked to issues without needing to visit the "Repository" tab first? Perhaps a configuration setting I'm missing or a cron job that could help?

I appreciate any insights or solutions you might have.

Thank you!