api: exposed modified added/modified/deleted functions of commit to return only paths....

api: exposed modified added/modified/deleted functions of commit to return only paths. This combined with full text search build for certain repositories that each commit contains lots of file changes results in *huge* (10x in some cases) performance gain.

dan - - Load All Authors

File last commit:

r4111:e62fd087 default


                r4242:a0c2e883

stable

Download file

             issue-trackers.rst
        
                    76 lines
            
             | 2.0 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 |RCE| 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:

Open :menuselection:`Admin --> Settings --> Issue Tracker`.
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.
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