##// END OF EJS Templates
rhodecode-enterprise-ce
RSS
auth: don't break hashing in case of user with empty password....
auth: don't break hashing in case of user with empty password. In some cases such as LDAP user created via external scripts users might set the passwords to empty. The hashing uses the md5(password_hash) to store reference to detect password changes and forbid using the same password. In case of pure LDAP users this is not valid, and we shouldn't raise Errors in such case. This change makes it work for empty passwords now.
lisaq - - Load All Authors

File last commit:

r645:c8c27324 default
r2203:8a18c3c3 default
Show More
issue-trackers.rst
81 lines | 2.4 KiB | text/x-rst | RstLexer
/ docs / issue-trackers / issue-trackers.rst
History | Annotation | Raw |Copy content |Copy permalink

Issue Tracker Integration

You can set an issue tracker connection in two ways with |RCE|.

  • At the instance level, you can set a default issue tracker.
  • At the |repo| level, you can configure an integration with a different issue tracker.

To integrate |RCM| with an issue tracker, you need to define a regular expression that will fetch the issue ID stored in commit messages, and replace 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

You can configure specific |repos| to use a different issue tracker than the default one. See the instructions in :ref:`repo-it`

Jira Integration

  • Regex = (?:^#|\s#)(\w+-\d+)
  • URL = https://myissueserver.com/issue/${id}
  • 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-