auth: add scope and login restrictions to rhodecode plugin, and scope restriction to token plugin....

auth: add scope and login restrictions to rhodecode plugin, and scope restriction to token plugin. - allows limiting the usage of builtin auth to HTTP only (so force usage of tokens) - allows migration to something like saml keeping only super-admin for login.

lisaq - - Load All Authors

File last commit:

r645:c8c27324 default


                r3392:5cc5c872

default

Download file

             jira.rst
        
                    27 lines
            
             | 813 B
            
                | text/x-rst
            
             |
                RstLexer

/ docs / integrations / jira.rst

History | Annotation | Raw |Copy content |Copy permalink

JIRA integration

Important

JIRA integration is only available in |RCEE|.

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.

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 the transition status id in the Workflow section of JIRA.

Once you have the transition status id, you can create a JIRA integration as outlined 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