Hi @TanyapongS ,
Thanks for reaching out to community.
There are points that can be achieved but shouldn't be achieved & this requirement is one of them.
Let me explain the reason:
1. Project milestones symbolizes an achievement
2. You can also consider them as checkpoints for crucial events like Go Live etc.
3. Milestone has no duration and typically no resources because it is to indicate the achievement of a crucial point in your project.
4. Stakeholders typically keep an eye on the milestones - whether they are achieved as planned to get a sense if project is on schedule. They do not have time & energy to see all the tasks - the lengthy WBS.
Now if you start adding duration to these milestones as well then what is the difference between tasks and milestone tasks.
5. Typically milestones are also defined for phase completion - This phase is a collection of tasks which have duration - The idea of milestone keeping at the end of phase is to indicate that all the tasks are done hence phase is done, but since it is an indication - a point in time in that project - hence milestone does not span over a duration.
6. Think of following use case:
USE CASE: As a Portfolio manager of 'Application Modernization' portfolio, I would like to track milestones of all the projects in my portfolio so that I can get the sense of all important activities in a glance over a timeline.
If required I can get the list of milestones in one click - basically by expanding the item.
I would strongly recommend not to customize milestones in the system. I would also recommend to understand the objective behind this ask; in other words rather than "how"; get an idea about "what" - what is that business users are trying to achieve. Based on that you decide the best way to achieve their ask.
Customizing milestone - BIG NO !!
Thank You!
Namita Mishra
