When assigning a Task to a Project take Area from Project Area
When you move or assign a task to a Project it does not automatically set the Areas to be that of the Project. It would be nice to avoid the extra step of assigning an area to the task when the associated Project is already assigned to an Area.
Hi Barry,
Thank you for your suggestion.
Short answer is: go ahead and leave the Area setting alone after you set the project. We will update the Area for you behind the scenes. A Project belongs to an Area anyway, so that logic just happens automatically.
Long answer: I can see where the confusion is since after you set the Project, we don’t update the Area setting in the dropdown. We used to but it caused a lot of confusion when users accidentally chose the wrong project. Example: User would choose Project B, which automatically switched to Area B. But Area B only has 1 project, so User no longer see all the projects. User thinks all projects have disappeared. We received a lot of tech support emails about that.
We also talked about always showing all projects in the list, but some accounts have a LOT of projects. Being able to filter that list by Area seemed important.
I hope you can understand how we came to this approach. I am respectfully declining this suggestion but if you have other ideas for this issue, I’ll be more than happy to discuss them.
Thanks and have a great day!
Mike