- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-08-2024 11:18 AM
I want the percent_complete field to increment if ANY closed state is selected. Right now it only increments if the Closed Complete is selected for a respective project task, ignoring Closed Incomplete and Closed Skipped.
I think it is a business rule but I couldn't see anywhere to adjust the valid state values to accommodate this change.
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-09-2024 10:45 PM
Hi @MBarrott ,
Hope you are doing well.
This functionality of persisting the %complete value when the task / project is marked as Closed skipped / Closed Incomplete was introduced in New York release.
Basically this feature allow the project manager or stakeholders to understand if some of its tasks are finished as closed incomplete / closed skipped just by looking at the %complete of the closed complete project.
This behaviour can be reverted, just by removing the skipped_state value.
I have created a recording to explain:
1) the feature highlights so you can decide whether to revert
2) Step to bring the behaviour back to pre-New York release. This means update the %complete of a task / project as100% irrespective of the closed state - closed incomplete, closed skipped, and closed complete.
Please mark the answer as correct if it answers your query.
Thank You!
Namita Mishra

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-08-2024 12:38 PM - edited 03-08-2024 12:39 PM
@MBarrott You can check these two business rules
1. Auto close milestones
2. Set Actual Work Start Value

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-09-2024 10:45 PM
Hi @MBarrott ,
Hope you are doing well.
This functionality of persisting the %complete value when the task / project is marked as Closed skipped / Closed Incomplete was introduced in New York release.
Basically this feature allow the project manager or stakeholders to understand if some of its tasks are finished as closed incomplete / closed skipped just by looking at the %complete of the closed complete project.
This behaviour can be reverted, just by removing the skipped_state value.
I have created a recording to explain:
1) the feature highlights so you can decide whether to revert
2) Step to bring the behaviour back to pre-New York release. This means update the %complete of a task / project as100% irrespective of the closed state - closed incomplete, closed skipped, and closed complete.
Please mark the answer as correct if it answers your query.
Thank You!
Namita Mishra
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2024 12:49 PM
Hi @Namita Mishra,
Thank you so much for this in depth video, this addressed my point and provided the exact solution that I needed.
Your video actually provides a sound justification for the skipped states and I have forwarded this reasoning to my management. We will likely hold off on this adjustment and see whether or not our PMO team would like to revert back to pre-New York setup.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-13-2024 12:46 AM
Thank you @MBarrott for the response.
Exactly that is why I shared the reasoning behind this change which we did in New York release. I am confident that now PMO will take an informed decision as they understand the background.
Thanks for the support & Happy SPM journey !!
Namita Mishra