Copy more data for synced items
complete
Vidas
Options what to copy:
- Child items (consider syncing completion state and schedule)
- Tags
- Custom fields
- Progress %
Questions to consider:
- What to do with tags and custom fields which do not exist in target workspace if synced copy is being placed not in the same workspace.
- Should tags and custom fields be only copied or synced as well?
Vidas
complete
Vidas
in progress
Vidas
planned
Kamilla Vit
In progress statuses; Custom fields; completion % during the creation (if item has 25% added, synced copy should have 25% too)
Vidas
under review
Vidas
Vidas
This makes sense. We have received multiple hints that at least initially copying child items can be usefull. Would you expect to have deep hierarchy sync for all levels of child items? I.E. sub-sub-child item?
Teddy Park
Vidas: Sorry for the late. Yes, I want it to copy all the sub-child items recursively.
Vidas
Teddy Park: one more question - would you expect all of those child items to function same way as top level item - syncing completion % and schedule?
Teddy Park
Vidas: Yes, definitely. For me, 'syncing' means both objects are same, like mirroring. From the user's point of view(or UX), it seems incomplete to perceive those two objects containing "different" properties(items, statuses) are "syncing".
Frankly, current sync-item function, which created without copying the 'child items' of originals, is also recognized as unstable for me.
Can we recognize/define it as "sync" when the state of information modified in one place is not reflected in another? This corresponds to a kind of 'copy by value,' and it seems complicated to see it as a straightforward 'copy by reference.'
Vidas
Teddy Park: yes, syncing not all properties is more complicated from UX perspective, and for now we do have this as logical choice. Because we see value in having flexibility to make one item in one workspace without assignee and have same item in another workspace with different assignee. Same goes to description or titles. For example when working high level to lower level workflows, roadmap item gets passed to a functional team and they do their own thing by decorating with relevant data.
Teddy Park
Vidas: Then, to satisfy all needs, need to add another button. Let's clearly state the two functions to reduce user confusion and use them for their purpose. (Each item should also be distinguished on the UI.)
Vidas
Teddy Park: thank you for your insights and time, will use it during refinement of next sync item iterations. We will do more synced/copied properties first and then rethink the concept itself.