Pinning shared files where original is checked out

kasti · Post by **kasti** » Tue May 17, 2005 6:28 am

We get the following error message when pinning a shared file which is checked out in another project:

fail: The object could not be modified because it or one of its children is checked out.

But there is no reason why this should not work. I need to be able to pin to a label even if development of the file has already continued.

Please let me know if this is intended functionionality and if it can be changed.

Thanks,
Herbert.

Post by **jclausius** » Tue May 17, 2005 7:07 am

Herbert:

This is a small bug.

The current work around is to release the checkout lock, pin the file in the different location, and then re-acquire the checkout lock.

Thanks for the report.

kasti · Post by **kasti** » Tue Jul 12, 2005 4:07 am

Hi,

Just tested this in Beta3, its not yet fixed. Any chance you can do this for 3.1 final?

Thanks,
Herbert.

lbauer · Post by **lbauer** » Tue Jul 12, 2005 2:59 pm

This is scheduled to be fixed in a later release.

kasti · Post by **kasti** » Wed Aug 24, 2005 3:58 am

Hi,

Could you tell me when we can have a fix for this? It's driving our configuration managers crazy. They have to repin many many files during a release, many of which are checked out. Its especially a problem when the person who has got the file checked out is not in the office....

Thanks,
Herbert.

lbauer · Post by **lbauer** » Wed Aug 24, 2005 8:01 am

The milestone for this bug is Vault 4.0, due out next year. I did bump it up in priority. Sorry I don't have anything more specific.