##// END OF EJS Templates
caches: use repo.lru based Dict cache. This LRUDict uses Timing Algo to not have to use locking...
caches: use repo.lru based Dict cache. This LRUDict uses Timing Algo to not have to use locking for the LRU implementation, this it's safer to use for dogpile. We used it before with beaker, so it's generally more stable.

File last commit:

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