Merge previously imported components

[tobiassjosten]

After a previous discussion here, I had to reconnect the GitHub app to get the import functionality working again. It does work now but, after the reconnection, all previously imported components now seem to be disassociated with the GitHub app, resulting in the app wanting to import every single GitHub repository again.

So now it seems we can re-import all components again and manually reconfigure the new ones before deleting the old ones. That's quite a lot of work. Or we continuously check each component manually to see if it's already been imported. Again, over time, a lot of work.

Is there a third option, where we can mark a repository as already imported so that it won't be listed as pending?

[Enrique Serrano Valle]

@tobiassjosten thank you so much for reaching out to us and sharing your experience with the re-importing of components and repositories. We appreciate your feedback, as it helps us improve the product and serve you better.

The system is designed to prevent duplicate imports of repositories that were originally created via GitHub import. So manually selecting repositories that were imported originally from GitHub with either of these options isn't expected to create a duplicate:

Ideally, when you manually select repositories that were originally imported from GitHub, they should not appear as pending for import again. Instead, these should be clearly labeled as "Created" on the manual selection screen:

However, we understand that there might be specific scenarios, such as repositories initially imported from Jira projects during onboarding, where duplicates could potentially arise if imported once more from GitHub. If this situation resonates with your experience, please let us know. Rest assured, reconnecting GitHub to Compass should not impact this process.

To ensure we can offer you the best possible support, could you kindly provide more details about where exactly the system is prompting you to import these components again? Additionally, understanding how the process is generating both new and existing components after the app reinstallation will greatly assist us in pinpointing any issues with the import selection menu not marking them as already "Created."

Your insights are invaluable to us, and we are committed to making this process as seamless as possible. Please feel free to share any additional details or questions you might have. We are here to help!

[tobiassjosten]

Thanks, Enrique! I appreciate the response.

I have no idea what's happened but I'm now in a state where we have 441 components in Compass, from ~220 in GitHub. So they have all been duplicated and I'm forced to go through all of these manually, one by one.

One set of these components — the newer ones — seems to be "connected" with the GitHub app, as they are recognized by Compass as already imported. The other set does not have this connection but has all the data we manually entered during our inventory.

So I'm at a loss for how best to proceed and it feels a little overwhelming. Please do advise.