Work Policy - Milestones

Kimberly, 

This occurred because you likely have the System Setting set to Work Policy = Fixed Duration. When adding new work items, this is what is used. Note that if you have child tasks beneath the Milestones are they Fixed Work or Duration? Note that this is a setting that you configure per object. If you specify the Project as Fixed Work, all other sub-work items will not automatically change and new sub work items will still use the default system setting for Work Policy for new Work Items.

This is System Setting:

No, It is set to Fixed Work.  And this is a new project that was created when it was set that way,  

Kimberly, 

Please open a ticket. Further investigation will be required. Please be sure to provide temporary access to your environment and link to the affected project, as well as this post and we will help you find the reason for this. 

Sincerely,

Clarizen Success Team

One other note slightly related to the question is that the Fixed Work/Duration/Units fields are defaults for all future items. If you change a project from Fixed Work to Fixed Duration, it will not automatically change all work items in that project to Fixed Duration. Also there are hierarchical rules in place since a project can have work items with different policies. The policy will be inherited from the direct parent inside of which you are creating the new object. So if you have a project that is Fixed Work, a sub project that is Fixed Duration, and create a milestone in the sub project, it will be Fixed Duration.

What I find helpful is to create a View with the Work Policy field so that you can quickly go through a project's hierarchy, view potential issues with policy, and make changes on the fly.