Work on it / Start task / Done button behaviour

[lgaertner]

Hello community,

I am currently stuck in a discussion with the Workfront support concerning the behaviour of the Work on it, Start Task, Done button.
Unfortunately, we are not making any progress here because we seem to have different views on the functionality of the button.
I'm just not sure whether I've fundamentally misunderstood something or whether there's a bug that the supporter can't understand.

We do have the following setup:

Team "Project Management" [PM] (Work On It Button on default setting)
Team "Operators" [OP] (Checkbox active Change the Work On It button to a Start button to automatically update the status of an item")

and the following workflow:

Team [PM] is assigned to the task and does the following:
- Assignment of Team [OP]
- Status change to Briefing (custom status equating to NEW)

Any operator, who is member of team [OP] and has this team set as hometeam opens the task and still sees the button as Work on it.

Those operators are not members of team[PM].

The button only changes to the desired Start Task for the operators, if the team [PM] is unassigned, or unassigned and assigned again.

For us this does not make sense as the way the button is displayed should depend on the team membership of the operator.

Is this a bug?

So, as the support case is active without progress for a while now, we internally discussed, if we could live without the Start task functionality and leave the button as Work on it.

As after the Operator is done with the task it should go back to the team [PM] (signalized by a different status), so I wanted to avoid that the task goes into the the default complete status by the operators. Therefore I configured the team settings accordingly. 

Unfortunately also here we have the same behaviour, the hometeam settings are not considered as long as the other team [PM] is assigned to the task before the team [OP].
I hope my explanations are comprehensible and you understand what I mean and I look forward to hearing your opinions and experiences on this topic.

Thanks in advance.

Regards

Lars

[skyehansen]

If I'm hearing you correctly, here's what I picture.

There are two teams being assigned at two different times, to the task. The team that is assigned first is considered the primary team (similar to the primary assignee, who automatically defaults to the user who was assigned first) and "owns" the task more than the subsequent teams.

The task "working on" button functionality appears to only consider the primary team's settings. This is why you're having to fiddle with the assignments.

I wouldn't necessarily call it a bug. The ability to add extra teams is very new, just arrived in the past year or two. Instead, I would term it an oversight (no one ever considered how it would work on an actual assignment with the Teams button), and the Support team will most likely come back and ask you to submit it as a feature request. 

Is this pretty much what you're asking about?