##// END OF EJS Templates
scm-app: allow to set documented pyro4 as scm_app_implementation....
scm-app: allow to set documented pyro4 as scm_app_implementation. The documented ini setting allows to set pyro4 as scm_app, while the backend code crashes on import of pyro4 module. This change allows to configure the app based on the .ini docs. if we pass pyro4 as backedn, we simply skip import and use the default pyro4 scm_app

File last commit:

r1:854a839a default
r632:064401fe default
Show More
repo-issue-tracker.rst
30 lines | 1.1 KiB | text/x-rst | RstLexer
/ docs / admin / repo-issue-tracker.rst

Repository Issue Tracker

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

  • At instance level, for more information see the :ref:`rhodecode-issue-trackers-ref` section.
  • At |repo| level. This allows you to configure a |repo| to use a different issue tracker to the default one.

Set an Issue Tracker per Repository

To configure a |repo| to work with a different issue tracker to the default one, use the following steps:

  1. Open :menuselection:`Admin --> Repositories --> repo name --> Edit --> Issue Tracker`

  2. Uncheck the :guilabel:`Inherit from default settings` box.

  3. Click :guilabel:`Add New`.

  4. Fill in the following settings:

    • :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.
  5. Click :guilabel:`Save`.