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

caches: use individual namespaces per user to prevent beaker caching problems....

caches: use individual namespaces per user to prevent beaker caching problems. - especially for mysql in case large number of data in caches there could be critical errors storing cache, and thus preventing users from authentication. This is caused by the fact that we used single namespace for ALL users. It means it grew as number of users grew reaching mysql single column limit. This changes the behaviour and now we use namespace per-user it means that each user-id will have it's own cache namespace fragmenting maximum column data to a single user cache. Which we should never reach.

lisaq - - Load All Authors

File last commit:

r645:c8c27324 default


                r2572:5b07455a

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