##// END OF EJS Templates
error-document: make sure the error document has registered helpers,...
error-document: make sure the error document has registered helpers, and uses only pyramid mechanics. - in some edge cases the renderer_globals are not called and we cannot rely on them - this should be a purely pyramid view not relying on any of pylons left overs.

File last commit:

r645:c8c27324 default
r1748:0fcdd9e3 default
Show More
redmine.rst
28 lines | 913 B | text/x-rst | RstLexer
dan
docs: updated docs for integrations, fixes #4137...
r552 .. _integrations-redmine:
Redmine integration
===================
.. important::
docs: updated integrations docs fix #4137
r645 Redmine integration is only available in |RCEE|.
dan
docs: updated docs for integrations, fixes #4137...
r552
.. important::
docs: updated integrations docs fix #4137
r645 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.
dan
docs: updated docs for integrations, fixes #4137...
r552
docs: updated integrations docs fix #4137
r645 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".
dan
docs: updated docs for integrations, fixes #4137...
r552
docs: updated integrations docs fix #4137
r645 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
dan
docs: updated docs for integrations, fixes #4137...
r552 :ref:`creating-integrations`.