##// END OF EJS Templates
fix(svn): cache path check similar like for git
fix(svn): cache path check similar like for git

File last commit:

r4374:659662b0 stable
r5565:78129c9a default
Show More
jira.rst
34 lines | 1.1 KiB | text/x-rst | RstLexer
dan
docs: updated docs for integrations, fixes #4137...
r552 .. _integrations-jira:
JIRA integration
================
.. important::
docs: updated integrations docs fix #4137
r645 JIRA 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
:ref:`rhodecode-issue-trackers-ref` section. The JIRA integration
only deals with altering JIRA issues.
dan
docs: updated docs for integrations, fixes #4137...
r552
The JIRA integration allows you to reference and change issue statuses in
JIRA directly from commit messages using commit message patterns such as
``fixes #JIRA-235`` in order to change the status of issue JIRA-235 to
docs: updated integrations docs fix #4137
r645 eg. "Resolved".
dan
docs: updated docs for integrations, fixes #4137...
r552
docs: updated integrations docs fix #4137
r645 In order to apply a status to a JIRA issue, it is necessary to find the
transition status id in the *Workflow* section of JIRA.
dan
docs: updated docs for integrations, fixes #4137...
r552
docs: updated integrations docs fix #4137
r645 Once you have the transition status id, you can create a JIRA integration
as outlined in :ref:`creating-integrations`.
docs: added mention how to change default integration templates.
r4374
.. note::
There's an option to configure integration templates.
Please see :ref:`integrations-rcextensions` section.
rcextensions examples are here: https://code.rhodecode.com/rhodecode-enterprise-ce/files/default/rhodecode/config/rcextensions/examples/custom_integration_templates.py