Bug: Reimporting a GitHub repository yields duplicate repository link

Steffen Opel _Utoolity_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 10, 2022

Other than the New Relic app, which properly syncs already existing components, reimporting a GitHub repository yields a duplicate repository link rather than an update/sync of the existing one.

Steps to reproduce

  1. Navigate to 'Create' => 'Import components' => 'GitHub'
  2. Click 'Select repositories'
  3. Select a repository with status '-' and click 'Select' to start the import
  4. Observe that the component has a single repository link
  5. Repeat steps 1 and 2, select the repository from step 3 with status 'Created' and click 'Select' to start the import
  6. Observe that the component has a second identical repository link

Actual result

A new repository link is created.

Expected result

The existing repository link is updated (synchronized).

2 comments

Josh Campbell
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 11, 2022

Thanks for the bug report Steffen, I've filed a ticket on our end to get this fixed up!

Like # people like this
Vadym Chepiga
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 15, 2022

@Steffen Opel _Utoolity_ It's fixed now ✅ 
Please, inform us in case it will be still reproducible for you.

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events