##// END OF EJS Templates
rhodecode-enterprise-ce
RSS
compare: using f_path shouldn't generate full range of commits....
compare: using f_path shouldn't generate full range of commits. - in case of comparing just 1 file the range of commits is not relevant. This in addition speeds rendering the compare page by a LOT.
lisaq - - Load All Authors

File last commit:

r645:c8c27324 default
r1262:fa7f32fd default
Show More
jira.rst
27 lines | 813 B | 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`.