# Cloning configurations with configuration specific repositories
**URL:** https://www.finalbuilder.com/forums/t/cloning-configurations-with-configuration-specific-repositories/6047
**Category:** Bugs
**Created:** [July 6, 2016, 11:14am UTC](https://www.finalbuilder.com/forums/t/cloning-configurations-with-configuration-specific-repositories/6047 "2016-07-06T11:14:24Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@remko.seelig](https://www.finalbuilder.com/forums/u/remko.seelig)
#### Post date: [July 6, 2016, 11:14am UTC](https://www.finalbuilder.com/forums/t/cloning-configurations-with-configuration-specific-repositories/6047/1 "2016-07-06T11:14:24Z")
Hi, I just ran in a situation that appears to be a bug (low severity I guess):
When cloning a configuration that has a configuration specific repository, the repository is selected for the cloned project but not visible. However, when running builds it’s reported in the changeset. I had to promote the repository to global or project and it then became visible and selected in the second tab (repository) and I was able to deselect it.
Can’t think of a way this would harm, but just wanted to report it anyway. Either the repository should be deselected (but would create a non-working clone) or it may be selected in the clone but the associated repositories that are scoped as configuration should then be promoted to either project or global, depending on the target project for the clone. Maybe the user should be prompted on beforehand.
Kind regards,
Remko Seelig
---
### Author:  [@Sparky](https://www.finalbuilder.com/forums/u/Sparky)
#### Post date: [July 7, 2016, 8:15am UTC](https://www.finalbuilder.com/forums/t/cloning-configurations-with-configuration-specific-repositories/6047/2 "2016-07-07T08:15:10Z")
Hi Remko,
Thank you for reporting this. We have reproduced the issue (due to a conflict with another thread) and have implemented a fix for next version.