Copy project feature in 2018 causes new files to be read only?

[Anonymous]

Using the copy project feature in 2018 and it seems that when it copies a project whose files are marked read only, the new files created are made read only as well. This wasn't the case in previous versions (we recently upgraded from 2015 to 2018). Is there a setting somewhere to prevent it from copying the original file's properties? It isn't an insurmountable issue, but just seems strange that it changed somewhere between 2015 and 2018.

Also, we do not use Vault, so there's nothing involving that as the issue.

[zalant]

I can confirm that it does it on version 2017 and newer. 2015 does not exhibit the behavior. I'm installing 2016 right now to see exactly at which release it changed. I will also ask the product team whether this was an intentional change. Once I have both of those answers, I will post back here.

UPDATE: Looks like the change occurred after version 2015, as version 2016 exhibits the behavior of making the copies read-only.

[zalant]

I've checked with the product team and this change in behavior was not purposefully designed. It is currently being investigated for returning to the previous result, where the new project's files are not read-only. Sorry for the inconvenience.

[Anonymous]

any solution for this issue or any work around.. we are using Vault 2018..