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

Bitbucket branch deletion is not being reflected on Development Panel

XMLWordPrintable

      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

            Niels Kristian Jensen added a comment -

            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

            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 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!

            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!

            Daniel Olsen added a comment -

            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

            Luis Garcia added a comment -

            Any update on the status of this issue?

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

            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. 

            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. 

            john added a comment -

            Please fix this. https://community.atlassian.com/t5/Jira-questions/How-to-unlink-a-bitbucket-branch-from-the-JIRA-task/qaq-p/712305

            john added a comment - Please fix this.  https://community.atlassian.com/t5/Jira-questions/How-to-unlink-a-bitbucket-branch-from-the-JIRA-task/qaq-p/712305

            yeager-j added a comment -

            This still appears to be an issue. 

            yeager-j added a comment - This still appears to be an issue. 

            Garth Egbert added a comment -

            Does Jira have any update on the status of this issue?
            Thanks.

            Garth Egbert added a comment - Does Jira have any update on the status of this issue? Thanks.

            Angelo Loria added a comment - - edited

             This is still a mess. A data resync did not help in my case. @Taylor Pechacek, is this actively being worked on? It's been ten months since you said 'near future.'

            Angelo Loria added a comment - - edited  This is still a mess. A data resync did not help in my case. @Taylor Pechacek, is this actively being worked on? It's been ten months since you said 'near future.'

            Evgeny Bondarenko added a comment -

            Okay, workaround was corrected to "contact Atlassian for data resync".
            Should we do it every time we delete a branch in bitbucket?

            Evgeny Bondarenko added a comment - Okay, workaround was corrected to "contact Atlassian for data resync". Should we do it every time we delete a branch in bitbucket?

            Evgeny Bondarenko added a comment -

            "Near future" is already more then half a year.

            Could you describe, what means workaround "contact Atlassian support"?

            Evgeny Bondarenko added a comment - "Near future" is already more then half a year. Could you describe, what means workaround "contact Atlassian support"?

            Tobias Klöpfel added a comment -

            What's your definition of "near future" tpechacek?

            Tobias Klöpfel added a comment - What's your definition of "near future" tpechacek ?

            Taylor (Inactive) added a comment - - edited

            Update:

            We have verified this is the current behaviour, as Jira keeps all related branch information in the dev panel, even those that have been deleted or closed after a merge. We will be fixing this issue sometime in the near future. Thanks for your patience.

            Jira Software, PM

            Taylor (Inactive) added a comment - - edited Update: We have verified this is the current behaviour, as Jira keeps all related branch information in the dev panel, even those that have been deleted or closed after a merge. We will be fixing this issue sometime in the near future. Thanks for your patience. Jira Software, PM

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

                Created:
                Updated:
                Resolved: