##// END OF EJS Templates
rhodecode-enterprise-ce
RSS
pull-requests: changed the order of close-branch after merge, so we don't leave open heads....
pull-requests: changed the order of close-branch after merge, so we don't leave open heads. Branches will be closed, and then merged based on the close commit. This is a proper and recommended workflow for feature branches and close option.
marcink - - Load All Authors

File last commit:

r4374:659662b0 stable
r4436:37e7e17e default
Show More
jira.rst
34 lines | 1.1 KiB | text/x-rst | RstLexer
/ docs / integrations / jira.rst
History | Annotation | Raw |Copy content |Copy permalink

JIRA integration

Important

JIRA integration is only available in |RCEE|.

Important

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.

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 eg. "Resolved".

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.

Once you have the transition status id, you can create a JIRA integration as outlined in :ref:`creating-integrations`.

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