# Feature SPAR-75 - Remove work and progress estimates from type Milestone

Project: Stream Planning and Reporting
Status: new
URL: https://community.openproject.org/work_packages/SPAR-75

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers | Christophe Bliard |
| Designer | Parimal Satyal |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

#### Context

Since version 14.0, % Complete is tied to Work and Remaining work. Milestones have always had the ability to have these fields, and thus also have progress. Yet, a Milestone is by definition duration-less and cannot have progress. It is merely meant to be a checkpoint or marker in the timeline. 

This work package is to decide how we deal with this in the context of the recent changes to Progress. We can also choose to not address this issue in this work stream and decide to address it separately in a larger feature to intorduce Milestones are a completely separate type of object.

#### **Open points**

Questions to be resolved concerning Milestones (from <mention class="mention" data-id="74738" data-type="user" data-text="@Christophe Bliard">@Christophe Bliard</mention>, copied from <mention class="mention" data-id="54496" data-type="work_package" data-text="#54496">#54496</mention>):

  - How should they be displayed in the work package table view?  
    *\[Parimal: W/RM/%C values should be empty\]*
    
      - Does a milestone wp with rejected status have the little information icon saying that the values are not included for totals calculations?  
        *\[Parimal: No, it does not\]*
    
      - should % complete be shown at all when in status-based mode or should it stay unset?
    
      - should totals be computed and shown for milestone types?

  - Should the values be removed when changing type from task to milestone?  
    *\[Parimal: Yes they should be removed; a milestone doesn't have these values so it would be like if the new type did not have the fields to accomodate existing values\]*

  - Should we have a migration to remove all values for milestone-types?  
    *\[Parimal: Logically, yes. But I see the challenges around this\]*

  - Should the values be removed when the "is milestone" flag is changed on a work package status?  
    *\[Parimal: Logically yes. Although I'm not sure why it's necessary to have multiple types defined as milestones; might need historical context to understand this)*

#### Related

<mention class="mention" data-id="54496" data-type="work_package" data-text="###54496">###54496</mention>