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

integrations: added branch_head into URL variables. This allow triggering more explicit...

integrations: added branch_head into URL variables. This allow triggering more explicit build on webhooks/jenkins. branch_head is the last commit of pushed branch so the build system doesn't have to figure it out itself. - in often updated projects without this explicit specified it could happen that the pushed braanch could change when CI systems fetches the code.

lisaq - - Load All Authors

File last commit:

r645:c8c27324 default


                r2864:9b105d43

stable

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