u/pc/rhodecode-enterprise-ce-fork-pc Files · docs/integrations/jira.rst

auth: don't break hashing in case of user with empty password....

auth: don't break hashing in case of user with empty password. In some cases such as LDAP user created via external scripts users might set the passwords to empty. The hashing uses the md5(password_hash) to store reference to detect password changes and forbid using the same password. In case of pure LDAP users this is not valid, and we shouldn't raise Errors in such case. This change makes it work for empty passwords now.

lisaq - - Load All Authors

File last commit:

r645:c8c27324 default


                r2203:8a18c3c3

default

Download file

             jira.rst
        
                    27 lines
            
             | 813 B
            
                | text/x-rst
            
             |
                RstLexer
            
             / docs / integrations / jira.rst
          
                    History
                
                 |
                  Source
                 | Raw
                 |Copy content
                 |Copy permalink

        dan
    
docs: updated docs for integrations, fixes #4137...

              r552
            
      .. _integrations-jira:

      JIRA integration

      ================

      .. important::

        lisaq
    
docs: updated integrations docs fix #4137

              r645
            
          JIRA integration is only available in |RCEE|.

        dan
    
docs: updated docs for integrations, fixes #4137...

              r552
            
      .. important::

        lisaq
    
docs: updated integrations docs fix #4137

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

        dan
    
docs: updated docs for integrations, fixes #4137...

              r552
            
      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

        lisaq
    
docs: updated integrations docs fix #4137

              r645
            
      eg. "Resolved".

        dan
    
docs: updated docs for integrations, fixes #4137...

              r552
            
        lisaq
    
docs: updated integrations docs fix #4137

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

        dan
    
docs: updated docs for integrations, fixes #4137...

              r552
            
        lisaq
    
docs: updated integrations docs fix #4137

              r645
            
      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

dan docs: updated docs for integrations, fixes #4137...	r552	.. _integrations-jira:

		JIRA integration
		================

		.. important::

lisaq docs: updated integrations docs fix #4137	r645	JIRA integration is only available in \|RCEE\|.

dan docs: updated docs for integrations, fixes #4137...	r552
		.. important::

lisaq docs: updated integrations docs fix #4137	r645	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.
dan docs: updated docs for integrations, fixes #4137...	r552

		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
lisaq docs: updated integrations docs fix #4137	r645	eg. "Resolved".
dan docs: updated docs for integrations, fixes #4137...	r552
lisaq docs: updated integrations docs fix #4137	r645	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.
dan docs: updated docs for integrations, fixes #4137...	r552
lisaq docs: updated integrations docs fix #4137	r645	Once you have the transition status id, you can create a JIRA integration
		as outlined in :ref:`creating-integrations`.