rhodecode-enterprise-ce Files · docs/admin/repo_admin/repo-issue-tracker.rst

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.

marcink - - Load All Authors

File last commit:

r3693:f470fd2e new-ui


                r4099:c12e69d0

default

Download file

             repo-issue-tracker.rst
        
                    30 lines
            
             | 1.1 KiB
            
                | text/x-rst
            
             |
                RstLexer
            
             / docs / admin / repo_admin / repo-issue-tracker.rst
          
                    History
                
                 |
                  Source
                 | Raw
                 |Copy content
                 |Copy permalink

        marcink
    
docs: updated documentation structure

              r3693
            
      .. _repo-it:

      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`.

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

marcink docs: updated documentation structure	r3693	.. _repo-it:

		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`.