Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-16851

Link to a commit in Developer Panel is not updated when repository name is changed

      Summary

      In Developer Panel, once you list the commits in Bitbucket, there is a hyperlink to the commit itself to the Bitbucket. However, when repository name is changed, the hyperlink does not get updated and is still pointing to the old repo.

      Environment

      • For Bitbucket commits only, using DVCS Connector in Jira Cloud

      Steps to Reproduce

      1. Connect Bitbucket Account to Jira Cloud through DVCS Connector
      2. In repository "Test", create some commits referencing to a Jira ticket (e.g. ABC-1)
      3. In ABC-1's Development Panel, each individual commit will be listed, and has a link such as:
      4. In Bitbucket, edit "Test" repository and rename it to "Trial" repository
      5. Check ABC-1's Development Panel again

      Expected Results

      In ABC-1's Development Panel, each individual commit will be listed, and has a new link such as:

      Actual Results

      In ABC-1's Development Panel, each individual commit is still listed, and still pointing to old link such as:

      Notes

      • Tried disconnecting and re-creating the Bitbucket Account through DVCS Connector again, doesn't work
      • Refereshing repositories list through DVCS connector doesn't work

      Workaround

      None at the moment

            [JSWCLOUD-16851] Link to a commit in Developer Panel is not updated when repository name is changed

            Dylan made changes -
            Labels New: bulk_close_12122019
            Dylan made changes -
            Resolution New: Won't Fix [ 2 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]

            Dylan added a comment -

            Due to an extended period of inactivity and low interest this bug has been auto-closed. If you’re still experiencing this issue, please comment and we’ll re-open to triage.

            Cheers,

            Atlassian

            Dylan added a comment - Due to an extended period of inactivity and low interest this bug has been auto-closed. If you’re still experiencing this issue, please comment and we’ll re-open to triage. Cheers, Atlassian
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: JSWCLOUD Bug Workflow [ 3193984 ] New: JAC Bug Workflow v3 [ 3474724 ]
            Status Original: Verified [ 10005 ] New: Gathering Impact [ 12072 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 2676706 ] New: JSWCLOUD Bug Workflow [ 3193984 ]
            SET Analytics Bot made changes -
            Support reference count Original: 1 New: 2
            Rodrigo Berto made changes -
            Assignee New: Rodrigo Berto [ rberto ]
            Rodrigo Berto made changes -
            Component/s New: Development Panel [ 46729 ]
            Component/s Original: DVCS Connector [ 46717 ]
            Rodrigo Berto made changes -
            Status Original: Open [ 1 ] New: Verified [ 10005 ]
            SET Analytics Bot made changes -
            Support reference count New: 1

              rberto Rodrigo Berto
              erezkyabdullah Ezra Alamsyah Rezky Abdullah (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: