# Assignee Specific Workflow **URL:** \ **Category:** Ideas & Features\ **Created:** [January 21, 2022, 3:35pm UTC](https://community.fibery.io/t/assignee-specific-workflow/2425 "2022-01-21T15:35:49Z")\ **Posts on this page:** 1\ **Showing post:** 14
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [January 23, 2022, 6:09pm UTC](https://community.fibery.io/t/assignee-specific-workflow/2425/14 "2022-01-23T18:09:36Z")
> [@Chr1sG](#): > > I don’t think there is a simple solution, but given how strong Fibery is/can be in terms of connectivity, it feels like it might be wise to choose to reap the value that comes from sub-dividing a task (separate workflows, and maybe more) so long as there is some clever, behind-the-scenes magic that maintains coherence, and minimises friction. This. 100% this. I was basically trying to articulate a similar view, but perhaps not doing it as succinctly or clearly. 😄 My hope is that the seemingly-logical (to me) splitting of tasks into separately tracked things can be done but avoid most of the downsides: keep it intuitive, reflect changes into a parent entity, and perhaps at the end roll it all up into the parent entity (destroy children but preserve work notes back into parent somehow). A fuller articulation of the downsides of the splitting approach would help inform possible solutions. As one example of a know problem here, getting comments together in one place seems interesting to think about. I don’t know that the contents of Comment Fields can be operated on in formulae at present, likewise Rich Text. But I can imagine something like concatenating all Comments from Child Entities into a single Rich Text, with e.g. labeling and dates for each, so you’d have a single Comments stream but still have it delineated what is what. [I previously proposed a “Conversation Field/View” and some interesting discussion resulted](https://community.fibery.io/t/conversations-for-integrations-email-integration/1721). If such a view existed, it would be ideal to be able to pass it “messages” via scripting, so that you could end up with a nicely formatted and consistent result for a situation like this. Likewise just spitballing here. 😉 --- _[View the full topic](https://community.fibery.io/t/assignee-specific-workflow/2425)._