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

dan - - Load All Authors

File last commit:

r552:9a0f45b0 default


                r632:064401fe

default

Download file

             jira.rst
        
                    26 lines
            
             | 817 B
            
                | text/x-rst
            
             |
                RstLexer

/ docs / integrations / jira.rst

History | Annotation | Raw |Copy content |Copy permalink

JIRA integration

Important

In order to make issue numbers clickable in commit messages see the :ref:`rhodecode-issue-trackers-ref` section. The JIRA integration only deals with altering JIRA issues.

Important

JIRA integration is only available in |RCEE|.

The JIRA integration allows you to reference and change issue statuses in JIRA directly from commit messages using commit message patterns such as fixes #JIRA-235 in order to change the status of issue JIRA-235 to eg. Resolved.

In order to apply a status to a JIRA issue it is necessary to find out the transition status id which can be found in the Workflow section of JIRA.

Once you have the transition status id, create a jira integration in :ref:`creating-integrations`.

	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