- Discussion Topics
- Other Resources
A field that implies a Person doesn't need to be an individual person. It can be a client name or ID, department, or other entity. Usage is up to you.
There are a number of attribute fields represented by droplists: Allocated To, Allocated By, Category, Status, Tags and Version.
Default values can be set in Preferences > Tasks > Defaults > Dynamic Droplists. These values are then available to all tasklists. A checkbox is provided to “Make this list read-only”. When this checkbox is NOT checked, you can enter a new value in a task and that value is then available to all other tasks in a given list. When checked, you must select a value from the default list. (Some fields allow multi-selection and some are single-select.)
Settings are available under menu > Tools > Preferences > Tasks > Defaults > Inheritable Attributes > Default Attributes. Several fields can have defaults set here. So when creating a new field the values here will be used, but they can still be manually set to other values.
Settings are available under menu > Tools > Preferences > Tasks > Defaults > Inheritable Attributes > Attribute Inheritance. Check desired fields to have subtasks inherit those values from their aren't when they are created. Many examples could be cited where this does and does not make sense. Choose the fields that make the most sense for your purposes.
There is also a setting here to “Continue to update subtasks as parent changes. As an example, if the Status of a parent task is set to Assigned, then all sub-tasks would similarly be Assigned. If the parent is set to Complete then it's assumed that all sub-tasks are also complete. That may or may not be logical for some project types, and while it might be reasonable for most tasks it might not apply in all cases.
:warning: Be careful when setting these flags that cause automatic changes of sub-tasks. If sub-tasks are not rigidly tied to the values of their parent tasks then you might not want to set some of these values.
Settings are available under menu > Tools > Preferences > User Interface > Tasklist Attributes> Date/Time Formatting. Note that these are application-level settings, not per-tasklist. For projects (clients, departments, etc) that require different formatting, see [Multiple Instances](UI-Multiple-Instances).
Time Estimates and Time Spent allow for a time value to be entered as an integer “1” or a floating-point value “1.25”. In the edit area with the numeric field is a dropdown list with values for (m)inutes, (H)ours, (D)ays, (W)eeks, (M)onths, and (Y)ears. You can quickly set the value of both the number and units. For example, on entering “4d” the 4 will stay in the numeric area while the dropdown will change to Days.