Move tasks between teams
We really need to be able to *easily* move TASKS between teams - e.g. drag and drop them or select and change the team. This should be able to be locked down by user if they don’t have access to a team - but it’s too easy to create a task in the wrong team and then have to fiddle around to move it
Design is beginning on this next week.
David Blevins commented
Setup flow maybe 30 minutes ago. Checked out the slack integration. UI looks great. Found this limitation. Filed in 2013? I'm a startup, so it guts me to say it, but the lack of resources more than the lack of the feature scares me a bit. I know how that fight goes -- you never have resources if people don't chose you because you don't have resources.
I'll continue our evaluations and check back periodically.
I'd really like to see this implemented, I can't work out how to move something between teams.
Is there any update on the status of this??
Admin: What is the update on this? It is now a year after design began and we are still grappling with a simple way to move tasks along.
I'm finding this is a deal breaker for me too.
Would also like an update on this since design work began a year ago. Right now, the lack of this feature severely impedes are ability to take full advantage of teams.
Just starting and in the trial period. Also bumped on the need to change tasks assignment between teams. Has this been done? If so, may I suggest that you make it easier to find :)
Hey guys. Any update yet on this?
Flow - I'm new (trialling software) and this is a major flaw. There has been no update on a fix that I can see on this thread for quite some time. It's obvious it's needed when can we expect a solution please?
Any updates on this?
Is this done yet? Thanks.
John Baeyens commented
John Baeyens commented
An absolute must !! When architecture finnished their part, the task needs to move on to engineering; this is today not possible (move a task from one team to another). Please Flow, make this a priority.
My company uses the email to flow feature extensively. We have about 8 departments which are set up as different teams. Our "traffic controller" has all requests auto forwarded to email@example.com from one email distribution group. Currently this Private Task can only be routed to one Team. Having the ability to move the task to a different team is a very important feature.
@scott - yep, I'm with you, it's *possible* to achieve the outcome at the moment, but it's not exactly user-friendly... and there's not really a good reason that I can see.
I hate to sound like a punk, but... seriously, how is this not possible and "not planned"? Moving Projects between workspaces is clunky enough, but how can I not merely type in a field in Edit mode to change the Workspace for a particular task? I know it's possible when creating a task from the "Overview" Workspace. How many organizations don't DAILY need to move tasks between workspaces, i.e. departments and teams? So we have to either go to a new workspace and create a new task or create a "Tasks to Move" project in every single workspace?! That. Is. Absolutely. Silly. Sorry to sound practically vitriolic. I'm not truly and largely upset, in the whole scheme of things. This isn't a dealbreaker, but it seems like Collaborative Task Management 101 that it should be possible. And this only has 38 votes?! Ok, rant over... I'll let democracy take its course.
...and the function is back.... thanks for getting that back in there.
really lame that you cant do this.
.....and unless I'm going crazy you can no longer move tasks between workspaces with the new release (ticket logged with support)
@Luke and @Jake....
You guys are killing me. "privacy and billing issues"? Really??
OK, let's assume there are - then maybe you can help me with this:
I am in the process of recruiting a new team member.
I have a workspace called "Recruiting" which is locked down to me and the other business owner.
Each new role is a project in the workspace.
I want to quickly forward all the applications that come through to my inbox and then move them to the correct workspace.
At the moment, that all go to my general company workspace - and to move them I have to fartarse about and stick them in a project, move the project, blah blah blah...
If you're not going to implement easy movement of tasks, then you need to have some way of capturing tasks OUTSIDE of a workspace and having them easily moved.
FLOW indicates that workspaces are things like "departments" or areas in the business - tasks DO move between departments of a business... Please consider the scenario whereby your customers are using flow INTERNALLY not just for client projects...
Come on... help me out here...