Customers
User information
 Loading ...
Show article in Knowledge Base

 Estimated time Export knowledge base Export     SubscribeSubscribe      Show article info

Field description - Estimated time

 

 

Short description:

 

Estimated time on an issue shows the predicted number of working hours needed to complete the issue.

 

 

 

Details:

 

Default name: Estimated time ("Est. time" in some places)

 

Terminology variations: None.

 

In-Use: Optional. This field can be set to be used in the issue field configuration.

 

Mandatory: Optional. This field can be set as mandatory, but need not be.

 

Data type: Decimal. This is the number of hours, in decimal. 0.5 equals 30 minutes.

 

Access restrictions: (Default) Created: "Read/Write" for all internal users, and "No access" for external or support users.  Editing: "Read/Write" for all internal users,  and "Read/write if owner or reporter" for external or support users.

 

Relationships/Dependencies: 

Remaining time: This is usually calculated from Estimated time minus Actual time.

 

 

Affected by these settings: 

Project > Settings > General, section "Sub-issues":

"Aggregate times from sub-issues on parents" - If "Estimated time" is checked in this setting, this field can no longer be set directly a the parent issue, but instead shows the sum of estimated times on its sub-issues. Estimated time can then only be set directly on issues that does not have sub-issues.

 

General > Settings > Issue configurations > Issue rules.

Estimated time can be used in issue rules, either as a criterion, or being set in the rule action.

 

 

Use cases: 

The Estimated time is used in planning how much time the upcoming work should take. After work has started (and reported) on an issue, you can compare the Actual time to the Estimated time to see where you are in your schedule (This is also visible in the "Progress" issue field).


User comments
 Loading ...