##// END OF EJS Templates
rhodecode-enterprise-ce
RSS
svn: fixed case of wrong extracted repository name for SSH backend. In cases...
svn: fixed case of wrong extracted repository name for SSH backend. In cases where we commited to a nested subdirs SVN reported the access path with the subdir paths in it. We couldn't then match that extended name into proper rhodecode repository for ACL checks. - Current implementation gives an slight overhead as we have to lookup all repositories - fixes #5606
lisaq - - Load All Authors

File last commit:

r645:c8c27324 default
r4281:5da17e74 default
Show More
redmine.rst
28 lines | 913 B | text/x-rst | RstLexer
/ docs / integrations / redmine.rst
History | Annotation | Raw |Copy content |Copy permalink

Redmine integration

Important

Redmine integration is only available in |RCEE|.

Important

In order to make issue numbers clickable in commit messages, see the section :ref:`rhodecode-issue-trackers-ref`. Redmine integration is specifically for altering Redmine issues.

Redmine integration allows you to reference and change issue statuses in Redmine directly from commit messages, using commit message patterns such as fixes #235 in order to change the status of issue 235 to eg. "Resolved".

To set a Redmine integration up, it is first necessary to obtain a Redmine API key. This can be found under My Account in the Redmine application. You may have to enable API Access in Redmine settings if it is not already available.

Once you have the API key, create a Redmine integration as outlined in :ref:`creating-integrations`.