##// END OF EJS Templates
pull-requests: add merge check that detects WIP marker in title. This will prevent merges in such case....
pull-requests: add merge check that detects WIP marker in title. This will prevent merges in such case. Usually WIP in title means unfinished task that needs still some work. This pattern is present in Gitlab/Github and is already quite common.

File last commit:

r3290:ac4e4e5a default
r4099:c12e69d0 default
Show More
issue-trackers.rst
81 lines | 2.4 KiB | text/x-rst | RstLexer
project: added all source files and assets
r1 .. _rhodecode-issue-trackers-ref:
Issue Tracker Integration
=========================
You can set an issue tracker connection in two ways with |RCE|.
docs: updated integrations docs fix #4137
r645 * At the instance level, you can set a default issue tracker.
* At the |repo| level, you can configure an integration with a different issue
project: added all source files and assets
r1 tracker.
docs: added SAML documentation....
r3290 To integrate |RCE| with an issue tracker, you need to define a regular
docs: updated integrations docs fix #4137
r645 expression that will fetch the issue ID stored in commit messages, and replace
project: added all source files and assets
r1 it with a URL. This enables |RCE| to generate a link matching each issue to the
target |repo|.
Default Issue Tracker Configuration
-----------------------------------
To integrate your issue tracker, use the following steps:
1. Open :menuselection:`Admin --> Settings --> Issue Tracker`.
2. In the new entry field, enter the following information:
* :guilabel:`Description`: A name for this set of rules.
* :guilabel:`Pattern`: The regular expression that will match issues
tagged in commit messages, or more see :ref:`issue-tr-eg-ref`.
* :guilabel:`URL`: The URL to your issue tracker.
* :guilabel:`Prefix`: The prefix with which you want to mark issues.
3. Select **Add** so save the rule to your issue tracker configuration.
Repository Issue Tracker Configuration
--------------------------------------
docs: updated integrations docs fix #4137
r645 You can configure specific |repos| to use a different issue tracker than the
default one. See the instructions in :ref:`repo-it`
project: added all source files and assets
r1
.. _issue-tr-eg-ref:
Jira Integration
----------------
* Regex = ``(?:^#|\s#)(\w+-\d+)``
jira: fixed #5439 documentation typo.
r2587 * URL = ``https://myissueserver.com/browse/${id}``
project: added all source files and assets
r1 * Issue Prefix = ``#``
Confluence (Wiki)
-----------------
* Regex = ``(?:conf-)([A-Z0-9]+)``
* URL = ``https://example.atlassian.net/display/wiki/${id}/${repo_name}``
* issue prefix = ``CONF-``
Redmine Integration
-------------------
* Regex = ``(issue-+\d+)``
* URL = ``https://myissueserver.com/redmine/issue/${id}``
* Issue Prefix = ``issue-``
Redmine (wiki)
--------------
* Regex = ``(?:wiki-)([a-zA-Z0-9]+)``
* URL = ``https://example.com/redmine/projects/wiki/${repo_name}``
* Issue prefix = ``Issue-``
Pivotal Tracker
---------------
* Regex = ``(?:pivot-)(?<project_id>\d+)-(?<story>\d+)``
* URL = ``https://www.pivotaltracker.com/s/projects/${project_id}/stories/${story}``
* Issue prefix = ``Piv-``
Trello
------
* Regex = ``(?:trello-)(?<card_id>[a-zA-Z0-9]+)``
* URL = ``https://trello.com/example.com/${card_id}``
* Issue prefix = ``Trello-``