Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-8622

Jira does not pick up branches in forked repositories until forced to check

    • Icon: Bug Bug
    • Resolution: Tracked Elsewhere
    • Icon: Low Low
    • None
    • 4.5.1
    • Integration - JIRA
    • On-Premises JIRA server and Bit Bucket Server

      After forking a repository in another project, when creating a branch from a JIRA issue the issue will not update anything under the development tab.

      Steps to Recreate
      1.) Fork a repository from another team project
      2.) Create a new branch from a JIRA issue
      3.) Observe the issue does not update its development section
      4.) Create a commit on that new branch that links to the JIRA issue
      5.) Observe the commit information populates the JIRA issue but the branch does not.

      Smart Commits do not work in this scenario as well.

          Form Name

            [BSERV-8622] Jira does not pick up branches in forked repositories until forced to check

            Thank you for the report, we are already tracking this as a feature request in BSERV-4541.

            Adam Brokes added a comment - Thank you for the report, we are already tracking this as a feature request in BSERV-4541 .

            rbutcher added a comment -

            Glad to hear its not just me. My company recently purchased JIRA/BitBucket/Bamboo and I was tasked with setting it all up and testing the workflows we expect to use. So, naturally I have been testing all the things. This is by no means a deal breaker for us, but it would be nice if it worked.

            Thanks for the quick confirmation

            rbutcher added a comment - Glad to hear its not just me. My company recently purchased JIRA/BitBucket/Bamboo and I was tasked with setting it all up and testing the workflows we expect to use. So, naturally I have been testing all the things. This is by no means a deal breaker for us, but it would be nice if it worked. Thanks for the quick confirmation

            We recently created some forked repos in our Stash 3.11.2 instance and discovered the same issue. Just hadn't had time to raise a JIRA issue.

            Deleted Account (Inactive) added a comment - We recently created some forked repos in our Stash 3.11.2 instance and discovered the same issue. Just hadn't had time to raise a JIRA issue.

              Unassigned Unassigned
              2ba80a0d4083 rbutcher
              Affected customers:
              1 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: