No option to manually alter the team for a Human Task (Activity) - can only select Me or User

[Berto2002]

Workflow assigned a Human Task thus to a team:

When I go to edit the assigned team (as super user) the team box is greyed-out and the Assign To box only allows "Me" or "User".

Something somewhere is preventing team from being an option on the manual edit?

[Peter Clough]

Are you listed as Manager of the Testing Team?

I think they're the only ones who can move something between teams.

Hornbill Platform Fundamentals - Human Tasks

The linked section of the docs here suggest that you need to be listed as a manager to move it to another team. Though I don't know if that's any other team, or just another team you also manage.

If you were set as the owner of the task, I believe that would also let you do it.

[Berto2002]

Yes I am manager of the testing team

I see your reference tho:

I see other workfows where I can also select Role, User, Team and Me so there's for sure a setting somewhere for this that I am missing

[Sam P]

Its been this way for a while, as a workaround if you assign it to yourself you should then be able to reassign to a Team.  

[Berto2002]

@Sam P interesting. Do you think there's been a change of behaviour in this way or new defect?

I can confirm that I assigned such a Human Task to myself and saved it...

... and then I WAS able to assign to another Team because the four options came-up.

Maybe the issue is that I was not Manager of the team it was originally assigned to

[Steve Giller]

47 minutes ago, Berto2002 said:

Do you think there's been a change of behaviour in this way or new defect?

Not, this has always been the behaviour.

[CraigP]

I have tried setting myself as the "manager" in own team but as far as I can tell it doesn't work to allow re-assignment as the documentation seems to suggest. Can anyone confirm whether the "manager" option has worked for them?

But yes, this has been like this for about a year and a half I think. Still waiting for team assignment to be fixed.

Inb4 "it's intended behaviour". No, I'm sorry but it is broken if being a member of the team allows you to re-assign it to a different team by first re-assigning it to yourself, but not from the initial team drop down. Either normal team members are intended to be able to re-assign tasks assigned to their team (and therefore should be able to use the dropdown immediately), or they're not (in which case there shouldn't be loopholes to do so).

As highlighted here, where a seasoned Hornbill administrator was not being aware they needed to assign it to themselves first, the current method to re-assign to different teams is not intuitive at all. As I say, it's been like this for over a year now and I still regularly have people ask me to re-assign their tasks for them because when they see a greyed out drop down then they obviously assume they don't have the ability to do it. In addition to this, you can easily re-assign tasks assigned to your roles, so why wouldn't you be able to re-assign tasks assigned to your teams?

And this doesn't even touch the negative impact the amendment made on reporting on tasks by team, where it doesn't automatically share it with the user's team when they assign it to themselves, thus meaning the rest of their team and manager lose sight of the task. Before you simply selected a user from a drop down under the team, then user was assigned and the team could still see it. Intuitive and significantly less clicks! Now the user is expected to somehow just know they need to save the task, re-open it again(!), and then re-share it with their team! And if they don't (who can blame them?), then any reports created for managers to see their teams tasks now need to have the usernames hardcoded into the report parameters to ensure tasks that got lost in this unintuitive mess get taken into account.

It's all well that this was done to fix an apparent bug, but the fact is the "solution" to fix it has caused all these issues, so imho clearly needs revisiting.

</rant>

Sorry, but this has been a huge bugbear for us since it changed, and it seems mad to me that there hasn't been more noise about it.

[Peter Clough]

We have also experienced numerous issues, primarily in our change processes, with being unable to reliably move tasks between teams, even when the person trying has the super admin role.

That might be a workaround, but it is hardly ideal. If nothing else, it would be good to get some clarification on how it is supposed to work, and how it is actually working, from Hornbill.

From our perspective, we've been thinking the Tasks is unhelpful from a management/admin/reporting perspective in any case, even though we like the functionality from an everyday usage perspective, and this is a part of that.

[JJack]

We also find this very inconvenient and clunky.
As an administrator, I get asked to reassign tasks that have got left behind (and are causing delay as they can't be completed), and I have to be a member of the team the task is currently with to be able to reassign it to another team - so the All My Teams view is never of much use to me, and there is the Edit/Me/Save, Edit/Team*/Save palaver too.
(And there's that thing where you have to start typing something in the box before it will show you any teams).

* I agree with comment above that when people assign to an individual rather than the team, there can be extra problems.

There are arguments in favour of not being able to easily deviate from a defined workflow but I don't think that is why this behaves as it does.

[Estie]

I agree with all the above comments and agree that a review of task assignment is definitely needed.

[Steve Giller]

19 hours ago, Peter Clough said:

even when the person trying has the super admin role.

If you're referring to the Super User Role, please note from the description: A super user should never log into the user application

Additionally, although this role overrides all rights and permissions it does not simply ignore the security model and grant complete access.