← Back to team overview

c2c-oerpscenario team mailing list archive

[Bug 619721] Re: Importance and urgence confusion in gtd module

 

Yes but this field comes from the task object itself and those values
make sense when gtd is not used. Once gtd is installed, i agree that
urgent and very urgent are less relevant but it's a minor issue. Some
tasks might use gtd and some others might not so i prefer not to change
it.

** Changed in: openobject-addons
       Status: New => Won't Fix

-- 
Importance and urgence confusion in gtd module
https://bugs.launchpad.net/bugs/619721
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject Addons Modules: Won't Fix

Bug description:
The object project.task.priority of the gtd module is disconcerting. Indeed, the gtd method must help user to determine task priority with two parameters: urgence AND importance.
So this ERP module sort task in a timebox to enhance most prior tasks.

Urgence should only be determine by the deadline of the task.
But, I think that for Importance item, there is a confusion. The items of importance field are: very low, low, medium, urgent and very urgent. According to me, they should be: very low, low, medium, important and very important. No?