Copy more data for synced items
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?
Log in to comment and vote
Comments12
Mar 1, 2023
Feb 14, 2023
Feb 13, 2023
Kamilla Vit
Feb 1, 2023
In progress statuses; Custom fields; completion % during the creation (if item has 25% added, synced copy should have 25% too)
Jan 26, 2023
Vidas
Jan 24, 2023
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
Feb 5, 2023
Vidas: Sorry for the late. Yes, I want it to copy all the sub-child items recursively.
Vidas
Feb 5, 2023
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?
Vidas
Feb 5, 2023
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.
Vidas
Feb 6, 2023
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.