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

Missing Overview tab warning about conflicts in Pull Request when page loaded on Diff tab

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 4.12.0
    • 4.1.0
    • Pull Requests
    • None

      Summary

      When there are pull-request with conflicts:

      • Opening the PR and Overview tab (default behaviour), there is an alert about the conflicts
      • Opening the PR on Diff or Commits tab and switching to Overview - the alert about conflicts will go missing

      Steps to Reproduce

      1. Have a repository with a file
      2. Create a pull request with conflicts on the file
      3. Look at the list of pull-requests and open conflicted one
      4. Overview tab should be opened by default
      5. At the top, below pull-request name, there should be an alert about the conflicts
      6. Switch to Diff or Commits tab
      7. Switch to Overview tab, alert about conflicts should still exist
      8. Switch to Diff or Commits tab
      9. Refresh page
      10. Switch to Overview tab
      11. Alert about conflicts will be missing

      Expected Results

      Overview tab should be showing the alert box about conflicts

      Actual Results

      Overview tab does not show the alert box about conflicts

            [BSERV-8514] Missing Overview tab warning about conflicts in Pull Request when page loaded on Diff tab

            Marcin added a comment -

            In 4.12 the "Conflicted" banner should correctly show when loading the page on a tab other than "Overview" and subsequently switching to the Overview tab.

            Marcin added a comment - In 4.12 the "Conflicted" banner should correctly show when loading the page on a tab other than "Overview" and subsequently switching to the Overview tab.

              mszczepanski Marcin
              vchoo Vivian C
              Affected customers:
              1 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: