2

I'd like to set my workflow up so that tasks can be initially "unassigned" - mostly because we've got a large number of tasks and it is unknown at this time who is going to pick them up and complete them.

I found an article which indicates that we should set up an "Unassigned" user and mark them as "Inactive" so that it doesn't go against our license.

We then set the project's primary contact to the "Unassigned" user and hey presto, all tasks will initially be assigned to this user until one of us picks it up.

We're using the Student/Startup license that only allows 2 developers, so we can't activate this user - even temporarily and we can't set the project's primary contact to an inactive account.

It seems like we're stuck between a rock and a hard place. Is there an alternative way to set up this functionality?

flag

1 Answer

5

You have to set this user as virtual. This way you don't waste a license.

link|flag

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.