Hi @Phil_Seeman, thanks for taking the time to see if this was feasible within your Flowsana service, and thanks @Jason_Woods for your recommendation - thank you too Ipb, unfortunately i’m only allowed to tag 2 people!
@Phil_Seeman unfortunately yeah - the hope was that we could have individual board projects per person, where they would only see tasks assigned to them; different columns representing priority order. Tasks would appear in their project when assigned to them via the project manager in a separate product project; if the project manager, or team member made a column change, this would be reflected in both the individuals project and product product, allowing easy delegation by the project manager, and clear viewing for the team member - at the moment our project manager’s have to manually follow column changes via task notifications, and manually update the column in the other project.
A good alternative would be for a filtering option where you can select ‘user can only see tasks assigned to them’, instead of it being explicit, and this to be enforceable on the admin end; for example, i could set the filter on a project to only show tasks for myself, then save it as default for everyone else; but then they’d see my projects, and not their own - we’ve tried this approach where we ask team members to set the filters themselves, but this then becomes an admin issue and an even bigger on-boarding issue, as it adds another step to getting up and running with Asana, and we have no way to control this on the admin end (or even see if people have set the correct filters).
Alternatively, we could move away from individuals having their own project, and have them work through their task list instead - but this doesn’t give the same amount of clarity as it’s hard to distinguish between projects (people might be working on multiple projects) and priority (if no timing is given, order is based on task creation date). From what we’ve seen, it’s more efficient for us to have someone (the project manager), manually update per-project column updates.
Although this works nicely for us, it does add a hefty time cost to the project management workflow - hearing your response, i think it’s clear we need to look at adopting an alternative workflow on Asana.
I was looking at trying out Flowsana before posting (had previously tried Zapier for another purpose), however from the thread i found, i was worried that Asana’s rule system had replaced your service (as the thread went quiet around the same time) - i’m glad to hear you’re still going and offer additional features and capabilities beyond Asana, I will definitely reconsider checking it out while we restructure things.