---
title: "Original estimate (Effort mode)"
canonical: "https://support.appfire.com/space/SPM/1918407058/Original%20estimate%20(Effort%20mode)"
format: markdown
---
> Macro (aura-html)

## Original estimate (Effort mode) (old navigation)

<details>
<summary>Expand</summary>

This is the default Effort Mode - the 'Original estimate' is evenly distributed between the working days in the task period. The non-working days are ignored in the calculation.

You can define the working and non-working days by editing the [Workload plans](https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918506352), [Holiday Plans](https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918505164), or [Absence Plans](https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918764834).

> ℹ️ Add the ‘Time Tracking’ field to your issue screen to enable Original Estimate, Remaining Estimate and Time Spent/Logged options.

![image](media://b0baee2c-0712-4581-99c6-9fdc7b4584b6)

## Effort calculation

For example: The 'date picker' type fields are used to determine both start and end position of the task. This means that changing the duration of a task does not change the Original Estimate field value. The BPV-4 task is estimated to take 2 weeks (Original estimate = 2w) and the duration of the task is 1 week. Calvin is assigned to the task. The Original Estimate value is evenly distributed over the duration period so the 80h / 5 d = 16h/d. As the allocation or the planned workload exceed the daily capacity, the workload and remaining capacity bars are colored red:

You can click on a task to see the task details:

![image](media://d196d99b-10f1-401d-b6ce-fb27695556a5)

You can stretch a task to avoid over-allocation. To do that, drag and drop the right edge of the task:

![image-20240117-105635.png](media://9daa9467-315d-4642-a0f7-139ccca3410c)

You can also switch to the 'Teams' view and assign a team comprising of multiple members who will work on that task. For example, the Team Smartwatch has four members and has a 32h/d capacity, which means that we can reduce duration of the task to three days and still be left with some remaining capacity:

![image-20240117-105655.png](media://53a365bf-0c12-4d80-9f05-ed23c8258b2f)

## Warnings 

Warnings can help you in resolving the most common problems. To enable Warnings go to View > Warnings.  If a task does not have an Original Estimate available, a red line contours the Task (if Warnings are enabled). Click on the task to show the warning in the task detail dialog:

> ℹ️ To locate tasks without a time estimate you can create a Quick filter: 'time estimate is empty'.

![image-20240117-105716.png](media://079b1059-ef16-484a-bf8d-31d5cf5a3a87)
</details>

## Original estimate (Effort mode) (new navigation)

<details>
<summary>Expand</summary>

This is the default Effort Mode - the 'Original estimate' is evenly distributed between the working days in the task period. The non-working days are ignored in the calculation.

You can define the working and non-working days by editing the [Workload plans](https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918506352), [Holiday Plans](https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918505164), or [Absence Plans](https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918764834).

> ℹ️ Add the ‘Time Tracking’ field to your issue screen to enable Original Estimate, Remaining Estimate and Time Spent/Logged options.

![original-estimate.png](media://b4516740-aded-439a-93e1-e86569603505)

## Effort calculation

For example: The 'date picker' type fields are used to determine both start and end position of the task. This means that changing the duration of a task does not change the Original Estimate field value. 

### Example

The BPV-4 task is estimated to take 2 weeks (Original estimate = 2w) and the duration of the task is 1 week. Calvin is assigned to the task. The Original Estimate value is evenly distributed over the duration period so the 80h / 5 d = 16h/d. As the allocation or the planned workload exceed the daily capacity, the workload and remaining capacity bars are colored red:

You can click on a task to see the task details:

![original-estimate-calculation.png](media://b12f715c-ea65-4c32-806c-aaba3063ca21)

You can stretch a task to avoid over-allocation. To do that, drag and drop the right edge of the task:

You can also switch to the 'Teams' view and assign a team comprising of multiple members who will work on that task. For example, the Team Smartwatch has four members and has a 32h/d capacity, which means that we can reduce the duration of the task to three days and still be left with some remaining capacity.

## Warnings 

Warnings can help you in resolving the most common problems. To enable Warnings, go to View > Warnings.  If a task does not have an Original Estimate available, a red line contours the Task (if Warnings are enabled). Click on the task to show the warning in the task detail dialog:

> ℹ️ To locate tasks without a time estimate, you can create a Quick filter: 'time estimate is empty'.

![calculation-warnings.png](media://93994f2a-cc75-4c3a-8c8e-0806a869680e)
</details>