- My View
Two things to consider leveraging for projects with large numbers of tasks in ServiceNow are:
1. If this project is similar to other projects in your organization, then build it once first and save it as a project template. That way the next time you need to build it you don't have to manually recreate dozens or hundreds of project tasks again.
2. You can also use Project Phases to group and organize sets of project tasks to make them more manageable. For example, a project that plans to incrementally release a product multiple times over the course of the project can use one Project Phase for each release. That will allow you to plan for dates and set milestones across each phase individually. You also have the ability to nest sub-projects inside of projects, and project tasks inside of project tasks, so you can end up with a hierarchy of work that you can click and drill down through. Although I personally prefer to use just Project > Project Phases > Project Tasks, because I find nesting too many layers can get confusing.