Allow Comments and Labels to Sync
Currently local changes to comments and or labels do not register as changes, and thus are unable to be synced outside of the initial commenting or labeling.
There have been many times I required a developer to add more details to their initial comments, and or had to fix a bad label, and had to change it in multiple places rather than in just one followed by telling everyone to sync.
I feel this is a very worth while feature to include; as that meta-data is what effectively describes a change-set and right now any changes to those items requires a lot of manual replication to update everyone's local repositories to match.
We have merged Lazlo's, Xorcist's and David's request into this one, so the vote count has all in consideration as it is almost the same request.
From this forum thread: https://forum.plasticscm.com/topic/22129-how-to-sync-labels-to-cloud/
I'd like to be able to sync labels and attributes without having to create dummy changesets. Currently that is not possible. That would be the equivalent of pushing just tags in Git, which is a common operation.
Example use case: We have someone on the team who has a "management" role for the development process that is likely to label changesets for "bookkeeping" purposes with our issue tracker and release cycles, but they likely won't be creating new changesets of their own. Currently, there's no way for them to do that kind of work and share it with the team unless they create dummy code edits that pollute the repository just to force a sync.
Jani Kärkkäinen commented
Voted, would definitely be useful in our process
Brian Judy commented
Upvote sync'ing of meta and code reviews
Yes, it probably should.
Problem is that tracking the attributes which is what I think you are missing, or the labels, to check whether the replica should be fired or not, would greatly impact performance.
Not something we are against, of course, and we should probably find a solution that is fast enough and good enough.
We need to wait for users to vote it up, though.
David Hernandez Cerpa commented
Sync views only push and pull pending changesets. However, when working with features like code reviews, new meta data is added to the branches without creating new changesets. In this situation, it is impossible for the user to know which branches have new meta data and they are forced to manually pull each branch to get the changes.
Besides the user experience issue, this breaks the concept of replication itself in my opinion, since the sync view is not keeping my local repo completely up to date with the remote.