Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-85858

Bitbucket branch deletion is not being reflected on Development Panel

      Summary

      Deleted branches which mention issue keys on Bitbucket are still visible on the issue's development panel

      Environment

      • JIRA Cloud integrated with Bitbucket cloud

      Steps to Reproduce

      • Create a branch mentioning an issue key
      • Delete the branch on Bitbucket

      Expected Results

      The branch info disappears from the issue's development panel

      Actual Results

      The branch information is still visible on the issue's development panel

      Notes

      Workaround

            [JRACLOUD-85858] Bitbucket branch deletion is not being reflected on Development Panel

            Tair Tidhar made changes -
            Component/s Original: Site - Settings - DVCS Accounts [ 46732 ]
            Component/s Original: Issue - Smart Commits [ 46731 ]
            Component/s Original: Issue - Development / Releases [ 46729 ]
            Component/s New: Integration - Dvcs accounts [ 77936 ]
            Component/s New: Issue - Smart Commits [ 77941 ]
            Component/s New: Placeholder [ 78004 ]
            Key Original: JSWCLOUD-16994 New: JRACLOUD-85858
            Symptom Severity Original: Severity 2 - Major [ 14431 ] New: Severity 3 - Minor [ 14432 ]
            Project Original: Jira Cloud [ 18511 ] New: Jira Platform Cloud [ 18514 ]

            Bug is present in Jira v8.3.5 - when was it fixed? @Rodrigo Berto

            Niels Kristian Jensen added a comment - Bug is present in Jira v8.3.5 - when was it fixed? @ Rodrigo Berto
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: JSWCLOUD Bug Workflow [ 3194137 ] New: JAC Bug Workflow v3 [ 3475149 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]

            cg_eoneill added a comment -

            I'm still seeing this problem. Deleted a branch that references the issue key, but it still shows on the Jira issue.

            cg_eoneill added a comment - I'm still seeing this problem. Deleted a branch that references the issue key, but it still shows on the Jira issue.
            Rodrigo Berto made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Verified [ 10005 ] New: Resolved [ 5 ]

            Hello everyone. This issue has been fixed and deleted branches should not be shown in the development panel anymore. We are going to proceed to close this issue, yet feel free to give us feedback or comment on it if you encounter unexpected behavior. Thanks!

            Rodrigo Berto added a comment - Hello everyone. This issue has been fixed and deleted branches should not be shown in the development panel anymore. We are going to proceed to close this issue, yet feel free to give us feedback or comment on it if you encounter unexpected behavior. Thanks!
            SET Analytics Bot made changes -
            UIS New: 1

            Would be nice to have an update from the Jira team. @Taylor Pechacek

            Daniel Olsen added a comment - Would be nice to have an update from the Jira team. @Taylor Pechacek

            Any update on the status of this issue?

            Luis Garcia added a comment - Any update on the status of this issue?

            The benefit (in our case, anyways) of using Bitbucket over a competitor are these features that tie Jira and Bitbucket together. Without these features working, there's no reason to stay in Bitbucket. 

            Angelo Loria added a comment - The benefit (in our case, anyways) of using Bitbucket over a competitor are these features that tie Jira and Bitbucket together. Without these features working, there's no reason to stay in Bitbucket. 

              Unassigned Unassigned
              htemp Heitor T (Inactive)
              Affected customers:
              24 This affects my team
              Watchers:
              33 Start watching this issue

                Created:
                Updated:
                Resolved: