Losing Shares and labels when branching and merging

[tsprague]

We've noticed that if we create a branch, the labels that are present on the source tree are not present in the branch. We also don't have shares between folders and files at child levels within the source tree. We think these are being lost when we perform merges back onto the source of the branch.

I'm thinking that this is new behavior for us. I'm pretty sure we've seen labels from the parent tree before. I'm also pretty sure that I can dig out some situations where the shares are being preserved too. We are using Vault 8 Standard. Should we be investigating a problem in our repository?

[Beth]

We've noticed that if we create a branch, the labels that are present on the source tree are not present in the branch.

That is correct behavior, because labels are tied to the location where they are created.

If a share is branched, then it becomes a branch, not another share.

Both of these items have been default behavior from about Vault 2.x.