##// END OF EJS Templates
rhodecode-enterprise-ce
RSS
auth-token: expose fetched token in unified way into request attribute....
auth-token: expose fetched token in unified way into request attribute. - This will allow re-using exposed access token for HTTP views in single place - We will support also exposing tokens from url if special _auth_token will be used as url param - We'll no longer require double logic for extraction of URL/HEADER auth-tokens and have a single place to extract it.
lisaq - - Load All Authors

File last commit:

r645:c8c27324 default
r4002:5f150e86 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`.