In this paper, we describe our proposal of researching a way of automatically identifying developers' tasks, starting from their interaction with their computers. The data used is collected by a tool which is fully automated, non-intrusive and general enough to accommodate any application that the developers might be using. The method is based on previous researches regarding the behavior of developers and the structures of their tasks. We consider three levels, in decreasing order of complexity: tasks, activities and actions. Our approach has two steps: mapping from actions to activities and from activities to tasks. We describe our approach, our hypotheses, our planned methodology and our expected results. We point also to some of our preliminary results.