{"id":15607,"date":"2023-04-13T04:25:15","date_gmt":"2023-04-13T04:25:15","guid":{"rendered":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/?post_type=article&#038;p=15607"},"modified":"2025-07-24T17:34:43","modified_gmt":"2025-07-24T12:04:43","slug":"getting-to-know-more-about-tasks-section-features","status":"publish","type":"article","link":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/article\/getting-to-know-more-about-tasks-section-features\/","title":{"rendered":"Getting to Know More About Tasks Section Features"},"content":{"rendered":"<p>This article provides a brief overview of several features available in the Tasks section of the Task Plan.<\/p>\n<p><iframe loading=\"lazy\" title=\"Understanding the Features of Tasks\" src=\"https:\/\/player.vimeo.com\/video\/1059980899?dnt=1&amp;app_id=122963\" width=\"500\" height=\"268\" frameborder=\"0\" allow=\"autoplay; fullscreen; picture-in-picture; clipboard-write; encrypted-media; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\"><\/iframe><\/p>\n<p>&nbsp;<\/p>\n<table style=\"height: 77px; width: 99.2704%; line-height: 10px; border-collapse: collapse; background-color: #f7f7f7; border-color: #f7f7f7; border-style: none;\">\n<tbody>\n<tr style=\"height: 108px; border-style: none; border-color: f7f7f7;\">\n<td style=\"width: 100%; height: 77px; background-color: #f7f7f7; border-style: none; border-color: #f7f7f7;\">\n<p style=\"text-align: left;\"><strong>Skip Ahead to:<\/strong><\/p>\n<p style=\"text-align: left; line-height: 10px;\"><a href=\"#Overview\">Overview<\/a><\/p>\n<p style=\"text-align: left;\"><a href=\"#AddTasks\">Add Tasks<\/a><\/p>\n<p style=\"text-align: left;\"><a href=\"#ModifyTasks\">Modify Tasks<\/a><\/p>\n<p style=\"text-align: left;\"><a href=\"#IndentandOutdent\">Indented Task<\/a><\/p>\n<p style=\"text-align: left;\"><a href=\"#IndentandOutdent\">Outdented Task<\/a><\/p>\n<p style=\"text-align: left;\"><a href=\"#DeleteTasks\">Delete Tasks<\/a><\/p>\n<p style=\"text-align: left;\"><a href=\"#Batchoption\">Batch Edit<\/a><\/p>\n<p style=\"text-align: left;\"><a href=\"#FilteringTasks\">Filtering Tasks<\/a><\/p>\n<p style=\"text-align: left;\"><a href=\"#CompleteTasks\">Complete Tasks<\/a><\/p>\n<p style=\"text-align: left;\"><a href=\"#CopyTasks\">Copy-Paste Tasks<\/a><\/p>\n<p style=\"text-align: left;\"><a href=\"#Assign\">Assign\/Unassign Resources to Tasks<\/a><\/p>\n<p style=\"text-align: left;\"><a href=\"#Hierarchies\">Hierarchies<\/a><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2><a id=\"Overview\"><\/a>Overview<\/h2>\n<p>The Tasks section of the Task Plan offers a wide range of options to help you manage your tasks effectively. In this article, we will go over some of the basic features and options available in the Tasks section of a Task Plan.<\/p>\n<h4><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-21832 size-full\" src=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/Screenshot-2025-07-23-at-6.54.40-PM.png\" alt=\"Task Plan\" width=\"2430\" height=\"1500\" srcset=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/Screenshot-2025-07-23-at-6.54.40-PM.png 2430w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/Screenshot-2025-07-23-at-6.54.40-PM-300x185.png 300w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/Screenshot-2025-07-23-at-6.54.40-PM-1024x632.png 1024w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/Screenshot-2025-07-23-at-6.54.40-PM-768x474.png 768w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/Screenshot-2025-07-23-at-6.54.40-PM-1536x948.png 1536w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/Screenshot-2025-07-23-at-6.54.40-PM-2048x1264.png 2048w\" sizes=\"(max-width: 2430px) 100vw, 2430px\" \/><\/h4>\n<h2>Tasks Section Features<a id=\"AddTasks\"><\/a><\/h2>\n<h3>Add Tasks<\/h3>\n<p data-start=\"348\" data-end=\"366\">To add a new task:<\/p>\n<ol data-start=\"368\" data-end=\"1016\">\n<li data-start=\"368\" data-end=\"488\">\n<p data-start=\"371\" data-end=\"488\">In the Task Plan grid view, select the hierarchy level to view all sub-tasks or collapse to a higher level as needed.<\/p>\n<\/li>\n<li data-start=\"489\" data-end=\"550\">\n<p data-start=\"492\" data-end=\"550\">Click the task <strong data-start=\"507\" data-end=\"522\">below which<\/strong> you want to add a new task.<\/p>\n<\/li>\n<li data-start=\"551\" data-end=\"728\">\n<p data-start=\"554\" data-end=\"728\">Hover over the task, click the <strong data-start=\"585\" data-end=\"601\">More Options<\/strong> icon, and select <strong data-start=\"619\" data-end=\"631\">Add Task<\/strong>.<br data-start=\"632\" data-end=\"635\" \/>Alternatively, use the <strong data-start=\"661\" data-end=\"673\">Add Task<\/strong> option directly from the toolbar or More Options menu.<\/p>\n<\/li>\n<li data-start=\"729\" data-end=\"888\">\n<p data-start=\"732\" data-end=\"888\">A new task appears with the same Planned Start and Finish dates as the task above it.<br data-start=\"817\" data-end=\"820\" \/>You can enter a name for the task and adjust the dates as needed.<\/p>\n<\/li>\n<li data-start=\"889\" data-end=\"1016\">\n<p data-start=\"892\" data-end=\"1016\">Fields such as <strong data-start=\"907\" data-end=\"918\">Planned<\/strong>, <strong data-start=\"920\" data-end=\"931\">Actuals<\/strong>, and <strong data-start=\"937\" data-end=\"950\">Baselined<\/strong> will automatically update as the task is assigned and progresses.<\/p>\n<\/li>\n<\/ol>\n<p data-start=\"1018\" data-end=\"1105\">Once added, the task is instantly saved and appears in the task hierarchy in real time.<\/p>\n<p>Learn more on how to add tasks automatically in the Task Plan using the Activity Matrix from <a target=\"_blank\" href=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/article\/how-to-add-a-litetask\/#Tasks\" rel=\"noopener\">here<\/a>.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-21239 size-full\" src=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Add.png\" alt=\"Add Task\" width=\"852\" height=\"354\" srcset=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Add.png 852w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Add-300x125.png 300w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Add-768x319.png 768w\" sizes=\"(max-width: 852px) 100vw, 852px\" \/><\/p>\n<p>The Add Task, Delete Task, Copy Task, Paste Task, Indent Task, and Outdent Task options are available by simply hovering over the task and clicking on the More Options icon, which displays a menu.<\/p>\n<p>When you add Tasks from the Task List view, you need to note these important rules:<\/p>\n<ul class=\"whs13\" type=\"circle\">\n<li class=\"p\">Task Dates will never be computed or changed by the system except when the dates get rescheduled to accommodate the date changes of other dependent tasks. So the efforts and or the allocation is recalculated to accommodate changes if any to the task dates, efforts, or allocation, but the dates are never altered by the system.<\/li>\n<li class=\"p\">If no resources are assigned to the task, then moving the planned Start and End dates for a task will move the task allocation also accordingly. If a resource is assigned and has not logged in efforts against the task too, the same is applicable. For example, if the initial planned Start Date was 01-Sept, the planned End Date was 05-Sept and allocation is available for the same duration. Pushing the Plan Start Date by 2 days to 03-Sept will push the planned End date and allocation days also by 2 days.<\/li>\n<li class=\"p\">For efforts logged in the timesheet for dates falling within the range of the Planned Start and End dates of a task, trying to move the planned Start Date will throw an alert. This informs the user that efforts are logged in the timesheet, so the planned Start Date cannot be altered. This is applicable for partial efforts or efforts for the entire duration falling under the planned Start and End dates of tasks. For example, if efforts are logged against 02-Sept against the task for which the Planned Start Date is 01-Sept, trying to move the Planned Start Date to 03-Sept will throw an alert informing the user of the efforts logged already.<\/li>\n<li class=\"p\">Selection of &#8216;Planned Start Date&#8217; and &#8216;Planned Finish Date&#8217; is mandatory while creating a new Task.<\/li>\n<li class=\"p\">The efforts get calculated from %allocation. When the Allocation level effort is changed, the % allocation gets re-calculated. If %allocation is changed then effort gets recalculated. For example, if a resource&#8217;s allocation is changed from 100% to 50%, then the effort for the 50% allocation gets recalculated and displayed.<\/li>\n<li class=\"p\">Selection of &#8216;Summary Task&#8217; is mandatory. The selection of the summary task decides the WBS code of the new task is added. The new task appears last within the hierarchy of selected &#8216;Summary Task&#8217;.<\/li>\n<li class=\"p\">The list of &#8216;Summary Tasks&#8217; displays only tasks that do not have any resources assigned to them. For existing summary tasks, you can assign resources. However, once resources are assigned to an existing summary task, no more child tasks can be added to it.<\/li>\n<li class=\"p\">&#8216;Planned Finish Date&#8217; must be equal to or greater than &#8216;Planned Start Date&#8217;. The Planned Start date cannot be later than the Actual Start date at resource allocation as well as task levels.<\/li>\n<\/ul>\n<p><strong>Notes:<\/strong><\/p>\n<ul class=\"whs3\" type=\"disc\">\n<li class=\"p-List\">Allocation start date having actuals posted against it is editable only in case the assignment is an\u00a0open assignment.<\/li>\n<li class=\"p-List\">Standard Code is code maintained for standard activities\/tasks by the Process Team in the organization, which helps to aggregate data in reports such as Timesheet Reports and computing metrics such as Rework Effort on the Analytics.<\/li>\n<li class=\"p-List\">The highest level summary task is created by default in your project to which you can add subtasks. It is named on the basis of the project ID entered when creating the project and can be edited.<\/li>\n<\/ul>\n<p>Common operations available for a Task are &#8211; &#8216;Enter Time&#8217; for the Task (available only for projects which have Time Tracking enabled i.e.\u2018Include in Timesheet\u2019 option selected for the Task Form), Close and open Time-Entry, Comments &amp; Attachments, \u00a0Linked Cards, and View the Activity Log.<a id=\"ModifyTasks\"><\/a><\/p>\n<h4><strong>Modify Tasks<\/strong><\/h4>\n<p data-start=\"307\" data-end=\"451\">After adding tasks, you can organize and structure your Task Plan by outlining the tasks. You can only edit tasks that are not marked as closed.<\/p>\n<ul>\n<li data-start=\"455\" data-end=\"572\">To modify the content of a task cell, click once to edit inline. Double-click to select the full content in the cell.<\/li>\n<li data-start=\"455\" data-end=\"572\">To change task duration, click the date field and select new dates using the calendar picker.<\/li>\n<li data-start=\"455\" data-end=\"572\">To <strong data-start=\"674\" data-end=\"684\">indent<\/strong> a task, hover over it, click the <strong data-start=\"718\" data-end=\"734\">More Options<\/strong> icon, and select <strong data-start=\"752\" data-end=\"767\">Indent Task<\/strong>. This turns it into a subtask of the nearest preceding task at a higher outline level.<\/li>\n<li data-start=\"455\" data-end=\"572\">To <strong data-start=\"860\" data-end=\"871\">outdent<\/strong> a task, select <strong data-start=\"887\" data-end=\"903\">Outdent Task<\/strong> to make it a summary task for the task that follows.<\/li>\n<li data-start=\"455\" data-end=\"572\">To assign or unassign resources\u2014or update assignment dates\u2014see the <a target=\"_blank\" href=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/article\/how-to-assign-unassign-resources-to-tasks\/\" rel=\"noopener\" class=\"\" data-start=\"1026\" data-end=\"1050\">Assigning Resources<\/a> section for help.<\/li>\n<\/ul>\n<p data-start=\"1074\" data-end=\"1210\">All changes are saved automatically in real time. If there are any issues, a validation message will appear with details for correction.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-21834 size-full\" src=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Modify-Task-1.png\" alt=\"Modify Task\" width=\"2404\" height=\"1420\" srcset=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Modify-Task-1.png 2404w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Modify-Task-1-300x177.png 300w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Modify-Task-1-1024x605.png 1024w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Modify-Task-1-768x454.png 768w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Modify-Task-1-1536x907.png 1536w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Modify-Task-1-2048x1210.png 2048w\" sizes=\"(max-width: 2404px) 100vw, 2404px\" \/><\/p>\n<p>o modify a task, single-click the task or select the task in the Grid listing, make changes, and save. Certain aspects of the Simple Scheduling task modifications are explained with help of the following scenarios:<\/p>\n<p><strong>Scenario 1: Modification to Planned Dates of Tasks without Actuals<\/strong><\/p>\n<p>Consider modification to plan dates for a task, to which resources are assigned but have not logged actuals.<\/p>\n<ul class=\"whs3\" type=\"disc\">\n<li class=\"p\">Modifying the Task Start\/End Date with dates within planned and assignment date ranges will modify the assignment dates. You can observe this in the following illustration:<\/li>\n<\/ul>\n<table class=\"whs25\" style=\"width: 85.5758%;\" width=\"100%\" cellspacing=\"0\">\n<colgroup>\n<col class=\"whs26\" \/>\n<col class=\"whs26\" \/>\n<col class=\"whs26\" \/><\/colgroup>\n<tbody>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs28\" style=\"width: 27.8785%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Task Details<\/strong><\/p>\n<\/td>\n<td class=\"whs29\" style=\"width: 28.6057%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Planned Task Dates<\/strong><\/p>\n<\/td>\n<td class=\"whs30\" style=\"width: 29.0906%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Assignment Dates<\/strong><\/p>\n<\/td>\n<\/tr>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs31\" style=\"width: 27.8785%;\" width=\"33.333%\">\n<p class=\"whs15\">Original Task Dates<\/p>\n<\/td>\n<td class=\"whs32\" style=\"width: 28.6057%;\" width=\"33.333%\">01-Sept to 05-Sept<\/td>\n<td class=\"whs33\" style=\"width: 29.0906%;\" width=\"33.333%\">01-Sept to 05-Sept<\/td>\n<\/tr>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs34\" style=\"width: 27.8785%;\" width=\"33.333%\">\n<p class=\"whs15\">Modified Task Dates<\/p>\n<\/td>\n<td class=\"whs35\" style=\"width: 28.6057%;\" width=\"33.333%\"><span style=\"color: blue;\">03-Sept<\/span>\u00a0to 05-Sept<\/td>\n<td class=\"whs36\" style=\"width: 29.0906%;\" width=\"33.333%\"><span style=\"color: blue;\">03-Sept<\/span>\u00a0to 05-Sept<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<ul>\n<li>Modifying the Task&#8217;s Planned Start Date\/End Date with a date outside planned date ranges will modify the assignment date. You can observe this in the following illustration, where the Planned Start Date is modified:<\/li>\n<\/ul>\n<table class=\"whs25\" style=\"width: 85.4545%;\" width=\"100%\" cellspacing=\"0\">\n<colgroup>\n<col class=\"whs26\" \/>\n<col class=\"whs26\" \/>\n<col class=\"whs26\" \/><\/colgroup>\n<tbody>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs28\" style=\"width: 27.9997%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Task Details<\/strong><\/p>\n<\/td>\n<td class=\"whs29\" style=\"width: 29.0905%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Planned Task Dates<\/strong><\/p>\n<\/td>\n<td class=\"whs30\" style=\"width: 28.3633%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Assignment Dates<\/strong><\/p>\n<\/td>\n<\/tr>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs31\" style=\"width: 27.9997%;\" width=\"33.333%\">\n<p class=\"whs15\">Original Task Dates<\/p>\n<\/td>\n<td class=\"whs32\" style=\"width: 29.0905%;\" width=\"33.333%\">02-Sept to 05-Sept<\/td>\n<td class=\"whs33\" style=\"width: 28.3633%;\" width=\"33.333%\">02-Sept to 04-Sept<\/td>\n<\/tr>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs34\" style=\"width: 27.9997%;\" width=\"33.333%\">\n<p class=\"whs15\">Modified Task Dates<\/p>\n<\/td>\n<td class=\"whs35\" style=\"width: 29.0905%;\" width=\"33.333%\"><span style=\"color: blue;\">01-Sept<\/span>\u00a0to 05-Sept<\/td>\n<td class=\"whs36\" style=\"width: 28.3633%;\" width=\"33.333%\"><span style=\"color: blue;\">01-Sept<\/span>\u00a0to 04-Sept<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<ul class=\"whs3\" type=\"disc\">\n<li class=\"p\">Modifying the \u00a0Task Start Date and End Date with dates outside the planned and assignment date ranges, will not modify the assignment dates. You can observe this in the following illustration:<\/li>\n<\/ul>\n<table class=\"whs25\" style=\"width: 85.5758%;\" width=\"100%\" cellspacing=\"0\">\n<colgroup>\n<col class=\"whs26\" \/>\n<col class=\"whs26\" \/>\n<col class=\"whs26\" \/><\/colgroup>\n<tbody>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs28\" style=\"width: 28.4845%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Task Details<\/strong><\/p>\n<\/td>\n<td class=\"whs29\" style=\"width: 29.393%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Planned Task Dates<\/strong><\/p>\n<\/td>\n<td class=\"whs30\" style=\"width: 27.8045%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Assignment Dates<\/strong><\/p>\n<\/td>\n<\/tr>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs31\" style=\"width: 28.4845%;\" width=\"33.333%\">\n<p class=\"whs15\">Original Task Dates<\/p>\n<\/td>\n<td class=\"whs32\" style=\"width: 29.393%;\" width=\"33.333%\">02-Sept to 05-Sept<\/td>\n<td class=\"whs33\" style=\"width: 27.8045%;\" width=\"33.333%\">03-Sept to 04-Sept<\/td>\n<\/tr>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs34\" style=\"width: 28.4845%;\" width=\"33.333%\">\n<p class=\"whs15\">Modified Task Dates<\/p>\n<\/td>\n<td class=\"whs35\" style=\"width: 29.393%;\" width=\"33.333%\"><span style=\"color: blue;\">01-Sept<\/span>\u00a0to 05-Sept<\/td>\n<td class=\"whs36\" style=\"width: 27.8045%;\" width=\"33.333%\">03-Sept to 04-Sept<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>Scenario 2: Modification to Planned Start Date of Task with Actuals<\/strong><\/p>\n<p>Consider modification to the Planned Start date for a task, to which resources are assigned and actual efforts have been tracked.<\/p>\n<ul class=\"whs3\" type=\"disc\">\n<li class=\"p\">Modifying the \u00a0Task&#8217;s Planned Start Date with a new date within the planned and assignment date ranges will throw an alert that the Planned Start cannot be after the first time log date. So, the Planned tasks and allocation remain unchanged. You can observe this in the following illustration where time has been logged for 01-Sept and the Planned Start is modified to 02-Sept:<\/li>\n<\/ul>\n<table class=\"whs25\" style=\"width: 83.0303%;\" width=\"100%\" cellspacing=\"0\">\n<colgroup>\n<col class=\"whs26\" \/>\n<col class=\"whs26\" \/>\n<col class=\"whs26\" \/><\/colgroup>\n<tbody>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs28\" style=\"width: 26.2965%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Task Details<\/strong><\/p>\n<\/td>\n<td class=\"whs29\" style=\"width: 27.7849%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Planned Task Dates<\/strong><\/p>\n<\/td>\n<td class=\"whs30\" style=\"width: 28.1862%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Assignment Dates<\/strong><\/p>\n<\/td>\n<\/tr>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs31\" style=\"width: 26.2965%;\" width=\"33.333%\">\n<p class=\"whs15\">Original Task Dates<\/p>\n<\/td>\n<td class=\"whs32\" style=\"width: 27.7849%;\" width=\"33.333%\">01-Sept to 05-Sept<\/td>\n<td class=\"whs33\" style=\"width: 28.1862%;\" width=\"33.333%\">01-Sept to 05-Sept<\/td>\n<\/tr>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs34\" style=\"width: 26.2965%;\" width=\"33.333%\">\n<p class=\"whs15\">Modified Task Dates<\/p>\n<\/td>\n<td class=\"whs35\" style=\"width: 27.7849%;\" width=\"33.333%\"><span style=\"color: red;\">02-Sept<\/span>\u00a0to 05-Sept<\/td>\n<td class=\"whs36\" style=\"width: 28.1862%;\" width=\"33.333%\">01-Sept to 05-Sept<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>&nbsp;<\/p>\n<table class=\"whs25\" style=\"width: 83.1515%;\" width=\"100%\" cellspacing=\"0\">\n<colgroup>\n<col class=\"whs26\" \/>\n<col class=\"whs26\" \/>\n<col class=\"whs26\" \/><\/colgroup>\n<tbody>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs28\" style=\"width: 26.6663%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Task Details<\/strong><\/p>\n<\/td>\n<td class=\"whs29\" style=\"width: 28.4845%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Planned Task Dates<\/strong><\/p>\n<\/td>\n<td class=\"whs30\" style=\"width: 27.9997%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Assignment Dates<\/strong><\/p>\n<\/td>\n<\/tr>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs31\" style=\"width: 26.6663%;\" width=\"33.333%\">\n<p class=\"whs15\">Original Task Dates<\/p>\n<\/td>\n<td class=\"whs32\" style=\"width: 28.4845%;\" width=\"33.333%\">01-Sept to 05-Sept<\/td>\n<td class=\"whs33\" style=\"width: 27.9997%;\" width=\"33.333%\">02-Sept to 05-Sept<\/td>\n<\/tr>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs34\" style=\"width: 26.6663%;\" width=\"33.333%\">\n<p class=\"whs15\">Modified Task Dates<\/p>\n<\/td>\n<td class=\"whs35\" style=\"width: 28.4845%;\" width=\"33.333%\"><span style=\"color: red;\">02-Sept<\/span>\u00a0to 05-Sept<\/td>\n<td class=\"whs36\" style=\"width: 27.9997%;\" width=\"33.333%\">02-Sept to 05-Sept<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>Scenario 3: Modification to Planned End Date of Task with Actuals<\/strong><\/p>\n<p>Consider modification to the Planned End Date for a task, to which resources are assigned and actual efforts have been tracked against.<\/p>\n<ul class=\"whs3\" type=\"disc\">\n<li class=\"p\">Modifying the \u00a0Task&#8217;s Planned Dates with a new date within the planned and assignment date ranges will change the Assignment Dates. You can observe this in the following illustration where time has been logged against 01-Sept and the Planned \u00a0Dates are modified:<\/li>\n<\/ul>\n<table class=\"whs25\" style=\"width: 84%;\" width=\"100%\" cellspacing=\"0\">\n<colgroup>\n<col class=\"whs26\" \/>\n<col class=\"whs26\" \/>\n<col class=\"whs26\" \/><\/colgroup>\n<tbody>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs28\" style=\"width: 26.3027%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Task Details<\/strong><\/p>\n<\/td>\n<td class=\"whs29\" style=\"width: 29.4542%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Planned Task Dates<\/strong><\/p>\n<\/td>\n<td class=\"whs30\" style=\"width: 28.2421%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Assignment Dates<\/strong><\/p>\n<\/td>\n<\/tr>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs31\" style=\"width: 26.3027%;\" width=\"33.333%\">\n<p class=\"whs15\">Original Task Dates<\/p>\n<\/td>\n<td class=\"whs32\" style=\"width: 29.4542%;\" width=\"33.333%\">01-Sept to 05-Sept<\/td>\n<td class=\"whs33\" style=\"width: 28.2421%;\" width=\"33.333%\">01-Sept to 05-Sept<\/td>\n<\/tr>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs34\" style=\"width: 26.3027%;\" width=\"33.333%\">\n<p class=\"whs15\">Modified Task Dates<\/p>\n<\/td>\n<td class=\"whs35\" style=\"width: 29.4542%;\" width=\"33.333%\">01-Sep<span style=\"color: blue;\">t<\/span>\u00a0to\u00a0<span style=\"color: blue;\">04-Sept<\/span><\/td>\n<td class=\"whs36\" style=\"width: 28.2421%;\" width=\"33.333%\">01-Sept to\u00a0<span style=\"color: blue;\">\u00a004-Sept<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<ul>\n<li>Modifying the \u00a0Task&#8217;s Planned End Date with a new date outside the planned and assignment date ranges, where the Planned Start Date remains the same will not change the Allocation Dates. You can observe this in the following illustration where time has been logged against 01-Sept and the Planned End Date is modified to 06-Sept:<\/li>\n<\/ul>\n<table class=\"whs25\" style=\"width: 82.7879%;\" width=\"100%\" cellspacing=\"0\">\n<colgroup>\n<col class=\"whs26\" \/>\n<col class=\"whs26\" \/>\n<col class=\"whs26\" \/><\/colgroup>\n<tbody>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs28\" style=\"width: 26.3052%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Task Details<\/strong><\/p>\n<\/td>\n<td class=\"whs29\" style=\"width: 30.179%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Planned Task Dates<\/strong><\/p>\n<\/td>\n<td class=\"whs30\" style=\"width: 26.3027%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Assignment Dates<\/strong><\/p>\n<\/td>\n<\/tr>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs31\" style=\"width: 26.3052%;\" width=\"33.333%\">\n<p class=\"whs15\">Original Task Dates<\/p>\n<\/td>\n<td class=\"whs32\" style=\"width: 30.179%;\" width=\"33.333%\">01-Sept to 05-Sept<\/td>\n<td class=\"whs33\" style=\"width: 26.3027%;\" width=\"33.333%\">01-Sept to 04-Sept<\/td>\n<\/tr>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs34\" style=\"width: 26.3052%;\" width=\"33.333%\">\n<p class=\"whs15\">Modified Task Dates<\/p>\n<\/td>\n<td class=\"whs35\" style=\"width: 30.179%;\" width=\"33.333%\">01-Sept to\u00a0<span style=\"color: blue;\">06-Sept<\/span><\/td>\n<td class=\"whs36\" style=\"width: 26.3027%;\" width=\"33.333%\">01-Sept to 04-Sept<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<ul>\n<li>Modifying the \u00a0Task&#8217;s Planned End Date with a new date outside the assignment date ranges will change the Assignment Date. You can observe this in the following illustration where time has been tracked against 01-Sept:<\/li>\n<\/ul>\n<table class=\"whs25\" style=\"width: 82.6667%;\" width=\"100%\" cellspacing=\"0\">\n<colgroup>\n<col class=\"whs26\" \/>\n<col class=\"whs26\" \/>\n<col class=\"whs26\" \/><\/colgroup>\n<tbody>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs28\" style=\"width: 25.5754%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Task Details<\/strong><\/p>\n<\/td>\n<td class=\"whs29\" style=\"width: 30.5451%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Planned Task Dates<\/strong><\/p>\n<\/td>\n<td class=\"whs30\" style=\"width: 26.5452%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Assignment Dates<\/strong><\/p>\n<\/td>\n<\/tr>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs31\" style=\"width: 25.5754%;\" width=\"33.333%\">\n<p class=\"whs15\">Original Task Dates<\/p>\n<\/td>\n<td class=\"whs32\" style=\"width: 30.5451%;\" width=\"33.333%\">01-Sept to 05-Sept<\/td>\n<td class=\"whs33\" style=\"width: 26.5452%;\" width=\"33.333%\">02-Sept to 05-Sept<\/td>\n<\/tr>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs34\" style=\"width: 25.5754%;\" width=\"33.333%\">\n<p class=\"whs15\">Modified Task Dates<\/p>\n<\/td>\n<td class=\"whs35\" style=\"width: 30.5451%;\" width=\"33.333%\">01-Sept to\u00a0<span style=\"color: blue;\">04-Sept<\/span><\/td>\n<td class=\"whs36\" style=\"width: 26.5452%;\" width=\"33.333%\">02-Sept to\u00a0<span style=\"color: blue;\">04-Sept<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>Scenario 4: Modification to Planned Dates of Closed Task and for Closed Allocation<\/strong><\/p>\n<p>Consider modification to Planned Dates for a closed task, and for a task where the allocation is closed.<\/p>\n<ul class=\"whs3\" type=\"disc\">\n<li class=\"p\">Modifying the \u00a0Task&#8217;s Planned Dates with a new date within the planned and assignment date ranges for a closed task. This will throw an alert that the task is already closed, so further modifications cannot be done. This applies to the Planned Start Date or Planned End Date of a closed task. You can observe this in the following illustration, where efforts were logged for 02-Sept and 03-Sept and the task was completed on 03-Sept:<\/li>\n<\/ul>\n<table class=\"whs25\" style=\"width: 80.481%;\" width=\"100%\" cellspacing=\"0\">\n<colgroup>\n<col class=\"whs26\" \/>\n<col class=\"whs26\" \/>\n<col class=\"whs26\" \/><\/colgroup>\n<tbody>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs28\" style=\"width: 24.999%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Task Details<\/strong><\/p>\n<\/td>\n<td class=\"whs29\" style=\"width: 28.0549%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Planned Task Dates<\/strong><\/p>\n<\/td>\n<td class=\"whs30\" style=\"width: 31.0724%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Assignment Dates<\/strong><\/p>\n<\/td>\n<\/tr>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs31\" style=\"width: 24.999%;\" width=\"33.333%\">\n<p class=\"whs15\">Original Task Dates<\/p>\n<\/td>\n<td class=\"whs32\" style=\"width: 28.0549%;\" width=\"33.333%\">01-Sept to 05-Sept<\/td>\n<td class=\"whs33\" style=\"width: 31.0724%;\" width=\"33.333%\">01-Sept to 05-Sept<\/td>\n<\/tr>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs34\" style=\"width: 24.999%;\" width=\"33.333%\">\n<p class=\"whs15\">Modified Task Dates<\/p>\n<\/td>\n<td class=\"whs35\" style=\"width: 28.0549%;\" width=\"33.333%\">\n<p class=\"whs37\">02-Sept to 04-Sept<\/p>\n<\/td>\n<td class=\"whs36\" style=\"width: 31.0724%;\" width=\"33.333%\">01-Sept to 05-Sept<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<ul>\n<li>Similarly, modify the \u00a0Task&#8217;s Planned Dates with a new date within the planned and assignment date ranges for a task with closed allocation. This will throw an alert that the date change will affect the closed allocation, which is not allowed. This applies to the Planned Start Date or Planned End Date of a task with closed allocations. You can observe this in the following illustration, where efforts were logged for 02-Sept and 03-Sept and the allocation was closed on 03-Sept:<\/li>\n<\/ul>\n<table class=\"whs25\" style=\"width: 84.2424%;\" width=\"100%\" cellspacing=\"0\">\n<colgroup>\n<col class=\"whs38\" \/>\n<col class=\"whs38\" \/>\n<col class=\"whs38\" \/>\n<col class=\"whs38\" \/><\/colgroup>\n<tbody>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs39\" style=\"width: 18.9394%;\" width=\"25%\">\n<p class=\"whs15\"><strong>Task Details<\/strong><\/p>\n<\/td>\n<td class=\"whs40\" style=\"width: 21.4848%;\" width=\"25%\">\n<p class=\"whs15\"><strong>Planned Task Dates<\/strong><\/p>\n<\/td>\n<td class=\"whs41\" style=\"width: 22.091%;\" colspan=\"1\" rowspan=\"1\" width=\"25%\">\n<p class=\"whs15\"><strong>Assignment Dates<\/strong><\/p>\n<\/td>\n<td class=\"whs41\" style=\"width: 21.7272%;\" width=\"25%\">\n<p class=\"whs42\"><strong>Assignment Dates<\/strong><\/p>\n<\/td>\n<\/tr>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs43\" style=\"width: 18.9394%;\" width=\"25%\">\n<p class=\"whs15\">Original Task Dates<\/p>\n<\/td>\n<td class=\"whs44\" style=\"width: 21.4848%;\" width=\"25%\">01-Sept to 05-Sept<\/td>\n<td class=\"whs45\" style=\"width: 22.091%;\" colspan=\"1\" rowspan=\"1\" width=\"25%\">01-Sept to 03-Sept<\/td>\n<td class=\"whs45\" style=\"width: 21.7272%;\" width=\"25%\">\n<p class=\"whs46\">01-Sept to 05-Sept<\/p>\n<\/td>\n<\/tr>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs47\" style=\"width: 18.9394%;\" width=\"25%\">\n<p class=\"whs15\">Modified Task Dates<\/p>\n<\/td>\n<td class=\"whs48\" style=\"width: 21.4848%;\" width=\"25%\">\n<p class=\"whs37\">02-Sept to 04-Sept<\/p>\n<\/td>\n<td class=\"whs49\" style=\"width: 22.091%;\" colspan=\"1\" rowspan=\"1\" width=\"25%\">01-Sept to 03-Sept<\/td>\n<td class=\"whs49\" style=\"width: 21.7272%;\" width=\"25%\">\n<p class=\"whs46\">01-Sept to 05-Sept<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>Scenario 5: Modification to Planned Dates beyond Allocation dates<\/strong><\/p>\n<p>Consider modification to Planned Dates for a task, beyond allocation dates.<\/p>\n<ul class=\"whs3\" type=\"disc\">\n<li class=\"p\">Modify the \u00a0Task&#8217;s Planned Start Date with a new date that is beyond the Assignment date. This will display an alert and the previously planned task and allocation dates are unchanged. You can observe this in the following illustration, where the Planned Start Date is 01-Sept and Planned End Date is 05-Sept and allocation is from 01-Sept to 05-Sept.<br \/>\nTrying to modify the Planned Start Date from 01-Sept \u00a0to 07-Sept will display an alert &#8211; Planned Start Date cannot be later than Planned End Date.<\/li>\n<\/ul>\n<table class=\"whs25\" style=\"width: 81.0909%;\" width=\"100%\" cellspacing=\"0\">\n<colgroup>\n<col class=\"whs26\" \/>\n<col class=\"whs26\" \/>\n<col class=\"whs26\" \/><\/colgroup>\n<tbody>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs28\" style=\"width: 27.2724%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Task Details<\/strong><\/p>\n<\/td>\n<td class=\"whs29\" style=\"width: 28.7997%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Planned Task Dates<\/strong><\/p>\n<\/td>\n<td class=\"whs30\" style=\"width: 25.0178%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Assignment Dates<\/strong><\/p>\n<\/td>\n<\/tr>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs31\" style=\"width: 27.2724%;\" width=\"33.333%\">\n<p class=\"whs15\">Original Task Dates<\/p>\n<\/td>\n<td class=\"whs32\" style=\"width: 28.7997%;\" width=\"33.333%\">01-Sept to 05-Sept<\/td>\n<td class=\"whs33\" style=\"width: 25.0178%;\" width=\"33.333%\">01-Sept to 05-Sept<\/td>\n<\/tr>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs34\" style=\"width: 27.2724%;\" width=\"33.333%\">\n<p class=\"whs15\">Modified Task Dates<\/p>\n<\/td>\n<td class=\"whs35\" style=\"width: 28.7997%;\" width=\"33.333%\">\u00a0<span style=\"color: red;\">07-Sept to 05-Sept<\/span><\/td>\n<td class=\"whs36\" style=\"width: 25.0178%;\" width=\"33.333%\">01-Sept to 05-Sept<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>Scenario 6: Modification to Planned Dates for Tasks without Actuals and overlapping Allocations<\/strong><\/p>\n<p>Consider modification to Planned Dates for a task without Actuals and overlapping allocation dates.<\/p>\n<ul class=\"whs3\" type=\"disc\">\n<li class=\"p\">Modify the \u00a0Task&#8217;s Planned Dates with dates that overlap the Assignment date. This will change the Allocation dates and consider the nearest inter-lapping dates. You can observe this in the following illustration, where the Planned Start Date is 02-Sept and Planned End Date is 10-Sept and allocation is from 05-Sept to 07-Sept.<\/li>\n<\/ul>\n<table class=\"whs25\" style=\"width: 86.4242%;\" width=\"100%\" cellspacing=\"0\">\n<colgroup>\n<col class=\"whs26\" \/>\n<col class=\"whs26\" \/>\n<col class=\"whs26\" \/><\/colgroup>\n<tbody>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs28\" style=\"width: 27.7572%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Task Details<\/strong><\/p>\n<\/td>\n<td class=\"whs29\" style=\"width: 28.6058%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Planned Task Dates<\/strong><\/p>\n<\/td>\n<td class=\"whs30\" style=\"width: 30.0602%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Assignment Dates<\/strong><\/p>\n<\/td>\n<\/tr>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs31\" style=\"width: 27.7572%;\" width=\"33.333%\">\n<p class=\"whs15\">Original Task Dates<\/p>\n<\/td>\n<td class=\"whs32\" style=\"width: 28.6058%;\" width=\"33.333%\">02-Sept to 10-Sept<\/td>\n<td class=\"whs33\" style=\"width: 30.0602%;\" width=\"33.333%\">05-Sept to 07-Sept<\/td>\n<\/tr>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs34\" style=\"width: 27.7572%;\" width=\"33.333%\">\n<p class=\"whs15\">Modified Task Dates<\/p>\n<\/td>\n<td class=\"whs35\" style=\"width: 28.6058%;\" width=\"33.333%\"><span style=\"color: blue;\">08-Sept<\/span>\u00a0to 10-Sept<\/td>\n<td class=\"whs36\" style=\"width: 30.0602%;\" width=\"33.333%\">\n<p class=\"whs50\">08-Sept to 08-Sept<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Similarly in the following example, you can see similar results.<\/p>\n<table class=\"whs25\" style=\"width: 86.6647%;\" width=\"100%\" cellspacing=\"0\">\n<colgroup>\n<col class=\"whs26\" \/>\n<col class=\"whs26\" \/>\n<col class=\"whs26\" \/><\/colgroup>\n<tbody>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs28\" style=\"width: 27.1512%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Task Details<\/strong><\/p>\n<\/td>\n<td class=\"whs29\" style=\"width: 28.8668%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Planned Task Dates<\/strong><\/p>\n<\/td>\n<td class=\"whs30\" style=\"width: 30.411%;\" width=\"33.333%\">\n<p class=\"whs15\"><strong>Assignment Dates<\/strong><\/p>\n<\/td>\n<\/tr>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs31\" style=\"width: 27.1512%;\" width=\"33.333%\">\n<p class=\"whs15\">Original Task Dates<\/p>\n<\/td>\n<td class=\"whs32\" style=\"width: 28.8668%;\" width=\"33.333%\">02-Sept to 10-Sept<\/td>\n<td class=\"whs33\" style=\"width: 30.411%;\" width=\"33.333%\">05-Sept to 07-Sept<\/td>\n<\/tr>\n<tr class=\"whs27\" valign=\"top\">\n<td class=\"whs34\" style=\"width: 27.1512%;\" width=\"33.333%\">\n<p class=\"whs15\">Modified Task Dates<\/p>\n<\/td>\n<td class=\"whs35\" style=\"width: 28.8668%;\" width=\"33.333%\">\u00a002-Sept to <span style=\"color: blue;\">04-Sept<\/span><\/td>\n<td class=\"whs36\" style=\"width: 30.411%;\" width=\"33.333%\">\n<p class=\"whs50\">04-Sept to 04-Sept<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>To delete one or more Tasks, select the task (s), click the\u00a0<strong>More Options<\/strong> icon, and select the\u00a0<strong>Delete<\/strong>\u00a0option.<\/p>\n<p><b>Note: <\/b>You can delete normal tasks only and not summary tasks, which have child tasks associated with them<\/p>\n<h3>Indent and Outdent Tasks<a id=\"IndentandOutdent\"><\/a><\/h3>\n<p data-pm-slice=\"0 0 []\">Your task plan will likely consist of a list of tasks organized in a hierarchy. This means some tasks are summary-level tasks, while others are child\/leaf-level tasks under those summary tasks. Summary tasks may represent different phases of a project or larger portions of work, whereas child tasks are the more detailed activities under these summary tasks. Summary tasks are typically displayed in greyed-out.<\/p>\n<p>You can create subtasks or adjust summary tasks using Indent or Outdent\u00a0functionality. To indent or outdent a task, simply right-click the desired task and select <strong>Indent<\/strong> or <strong>Outdent Task<\/strong> from the context menu or use the options under More Options.<\/p>\n<p>To learn more about indent and outdent failure details, <a target=\"_blank\" href=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/article\/indent-and-outdent-tasks\/\" rel=\"noopener\">click here<\/a>.<\/p>\n<h4 class=\"whs15\"><strong>Indented Task<\/strong><\/h4>\n<p class=\"whs16\">When you indent a task, it becomes a subtask of its immediate sibling task. For example, let\u2019s consider the following hierarchy of tasks:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-19922 size-full\" src=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Indent-1.jpg\" alt=\"Indent Task\" width=\"1022\" height=\"297\" srcset=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Indent-1.jpg 1022w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Indent-1-300x87.jpg 300w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Indent-1-768x223.jpg 768w\" sizes=\"(max-width: 1022px) 100vw, 1022px\" \/><\/p>\n<p>Now let\u2019s indent Task TSK44. The new hierarchy will look as follows:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-19923 size-full\" src=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Indent-2.jpg\" alt=\"Indent Task\" width=\"1022\" height=\"288\" srcset=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Indent-2.jpg 1022w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Indent-2-300x85.jpg 300w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Indent-2-768x216.jpg 768w\" sizes=\"(max-width: 1022px) 100vw, 1022px\" \/><\/p>\n<h4 class=\"whs15\"><strong><a id=\"Outdent\"><\/a>Outdented Task<\/strong><\/h4>\n<p>When you outdent a task, it becomes a summary task of all the subsequent sibling tasks. For example, let\u2019s consider a hierarchy of tasks:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-19924 \" src=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Outdent-1.jpg\" alt=\"Outdent Task\" width=\"549\" height=\"394\" srcset=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Outdent-1.jpg 1026w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Outdent-1-300x215.jpg 300w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Outdent-1-1024x735.jpg 1024w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Outdent-1-768x551.jpg 768w\" sizes=\"(max-width: 549px) 100vw, 549px\" \/><\/p>\n<p>Now let\u2019s outdent the Task TSK8. The new hierarchy will look as follows<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-19925 \" src=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Oudent-2.jpg\" alt=\"Outdent Task\" width=\"542\" height=\"391\" srcset=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Oudent-2.jpg 1022w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Oudent-2-300x216.jpg 300w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Oudent-2-768x553.jpg 768w\" sizes=\"(max-width: 542px) 100vw, 542px\" \/><\/p>\n<p>Some facts are listed below to note when you indent or outdent a task:<\/p>\n<ul class=\"whs3\" type=\"disc\">\n<li>\n<p data-pm-slice=\"0 0 []\"><strong>Indenting a Task:<\/strong> Indenting moves a task to a lower hierarchy level (to the right), making it a subtask of the nearest preceding task at a higher hierarchy\u00a0level. You can indent tasks across multiple levels to reflect your project&#8217;s structure.<\/p>\n<\/li>\n<li>\n<p data-pm-slice=\"0 0 []\"><strong>Summary Tasks:<\/strong> When you indent a task, the preceding task becomes a summary task. A summary task, which consists of subtasks, is displayed in greyed-out and outdented. It summarizes the information of its subtasks.<\/p>\n<\/li>\n<li>\n<p data-pm-slice=\"0 0 []\"><strong>Outdenting a Task:<\/strong> Outdenting moves a task to a higher level in the hierarchy. When you outdent, the task can either become a normal task or a summary task, which can represent different phases or major sections of the project. Summary tasks automatically update their information based on the subtasks underneath them.<\/p>\n<\/li>\n<\/ul>\n<p>The Following explains in detail how the sub-task data is rolled up to the summary task.<\/p>\n<ul class=\"whs13\" type=\"circle\">\n<li class=\"p-List2\">\n<p class=\"List2\">Roll-up of Task Planned data to Summary Tasks<\/p>\n<\/li>\n<li class=\"p-List2\">\n<p class=\"List2\">&#8216;Planned Start Date&#8217; of the summary task is the MINIMUM of the &#8216;Planned Start Date&#8217; of all child tasks<\/p>\n<\/li>\n<li class=\"p-List2\">\n<p class=\"List2\">&#8216;Planned Finish Date&#8217; of the summary task is the MAXIMUM of the &#8216;Planned Finish Date&#8217; of all child tasks<\/p>\n<\/li>\n<li class=\"p-List2\">\n<p class=\"List2\">&#8216;Planned Start Date&#8217; and &#8216;Planned Finish Date&#8217; of the summary task can&#8217;t be modified (it is not editable field)<\/p>\n<\/li>\n<li class=\"p-List2\">\n<p class=\"List2\">The &#8216;Planned Start Date&#8217; of the summary task is automatically set to MINIMUM (&#8216;Planned Start Date&#8217; of all child tasks if it is greater than MINIMUM (&#8216;Planned Start Date&#8217; of all child tasks).<\/p>\n<\/li>\n<li class=\"p-List2\">\n<p class=\"List2\">You can manually set the &#8216;Planned Start Date&#8217; of the summary task to earlier than the MINIMUM (&#8216;Planned Start Date&#8217; of all child tasks)<\/p>\n<\/li>\n<li class=\"p-List2\">\n<p class=\"List2\">The &#8216;Planned End Date&#8217; of the summary task is automatically set to MAXIMUM [&#8216;Planned Finish Date&#8217; of all child tasks] if it is less than MAXIMUM [&#8216;Planned Finish Date&#8217; of all child tasks].<\/p>\n<\/li>\n<li class=\"p-List2\">\n<p class=\"List2\">Roll-up of Task Actual dates to Summary Tasks<\/p>\n<\/li>\n<li class=\"p-List2\">\n<p class=\"List2\">&#8216;Actual Start&#8217; of the summary task is the MINIMUM of\u00a0 &#8216;Actual Start&#8217; of all child tasks<\/p>\n<\/li>\n<li class=\"p-List2\">\n<p class=\"List2\">&#8216;Actual Finish&#8217; of the summary task is the MAXIMUM of &#8216;Actual Finish&#8217; of all child tasks<\/p>\n<\/li>\n<li class=\"p-List2\">\n<p class=\"List2\">&#8216;Actual Start&#8217; and &#8216;Actual Finish&#8217; of the summary task cant be modified (it is a label)<\/p>\n<\/li>\n<li class=\"p-List2\">\n<p class=\"List2\">Roll-up of Task &#8216;Estimated Effort&#8217; and &#8216;Remaining Effort&#8217; to Summary Task<\/p>\n<\/li>\n<li class=\"p-List2\">\n<p class=\"List2\">&#8216;Estimated Effort&#8217; of a summary task is the SUM of &#8216;Assigned Effort&#8217; of all child tasks<\/p>\n<\/li>\n<li class=\"p-List2\">\n<p class=\"List2\">&#8216;Remaining Effort&#8217; of a summary task\u00a0 is the SUM of &#8216;Assigned Effort&#8217; of all child tasks<\/p>\n<\/li>\n<li class=\"p-List2\">\n<p class=\"List2\">Indent or outdent a task such that sub-tasks created share characteristics or that are planned to be completed in the same time frame under a summary task.<\/p>\n<\/li>\n<li class=\"p-List2\">\n<p class=\"List2\">If you need to change a summary task&#8217;s values, such as duration, update the individual sub-tasks accordingly. Summary task values are then recalculated.<\/p>\n<\/li>\n<\/ul>\n<p><strong>Notes:<\/strong><\/p>\n<ul class=\"whs13\" type=\"circle\">\n<li class=\"p-ListBullet\">\n<p class=\"ListBullet\">Placing tasks in a hierarchical order does not automatically create task dependencies (Task Dependency: When you link a task with another, you create a dependency of one task on another by setting a relationship between their start and finish dates. There are four kinds of task dependencies: Finish-to-start [FS], Start-to-start [SS], Finish-to-finish [FF], and Start-to-finish [SF].) Simple Scheduling supports only F-S dependencies between Tasks. For more details on task dependencies, <a target=\"_blank\" href=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/article\/defining-task-dependency\/\" rel=\"noopener\">click here<\/a>.<\/p>\n<\/li>\n<li class=\"p-ListBullet\">\n<p class=\"ListBullet\">After rearranging linked tasks in your outlined schedule, the task dependencies you set previously may no longer be relevant and you need to update them.<\/p>\n<\/li>\n<\/ul>\n<h3><a id=\"BatchAssign\"><\/a>Batch Assign<\/h3>\n<p>Assign Resources to Multiple Tasks using Batch Assign. Select the tasks by pressing CTRL (Windows) or CMD (iOS) then click the <strong>Batch Assign<\/strong> icon in the toolbar. The resource that is already assigned is listed with the corresponding check box selected.<\/p>\n<p>Select the check boxes for the required team members and click the\u00a0<b>Apply<\/b> button.<\/p>\n<h3>Delete Tasks<a id=\"DeleteTasks\"><\/a><\/h3>\n<p data-start=\"284\" data-end=\"567\">You can delete a selected task by clicking the <strong data-start=\"331\" data-end=\"347\">More Options<\/strong> icon and selecting <strong data-start=\"367\" data-end=\"382\">Delete Task<\/strong>. The <strong data-start=\"388\" data-end=\"398\">Delete<\/strong> button is also available in the task\u2019s Detail view. However, if time has already been entered and approved for that task assignment, the Delete option will be disabled.<\/p>\n<p data-start=\"569\" data-end=\"695\">If the task has dependencies (e.g., it is a predecessor to another task), deleting it will also remove those dependency links.<\/p>\n<p data-start=\"697\" data-end=\"1068\">For Task Plans using the <strong data-start=\"722\" data-end=\"748\">MS Project Task Module<\/strong>, the Delete button is not available. To delete a task, refer to the MS Project Help documentation.<br data-start=\"847\" data-end=\"850\" \/>Although MS Project allows deletion of tasks with approved time entries, when the Task Plan is synced back into Nimble, an alert will prompt you to re-include the task\u2014since its effort cannot be excluded from the plan.<\/p>\n<h2><a id=\"Batchoption\"><\/a>Batch Edit<\/h2>\n<p>Batch editing enables you to quickly apply the same changes to many tasks in a task at the same time without having to edit each one individually.<\/p>\n<p><strong>Steps for Batch Edit Operation:<\/strong><\/p>\n<ol class=\"whs2\" type=\"1\">\n<li class=\"p\">In the List view, select the items to be edited by clicking on the corresponding checkboxes. alternatively, select multiple tasks by pressing &lt;Shift + Click&gt; in Microsoft\u00ae Windows or &lt;Command-Click&gt; on the Mac OS.<\/li>\n<li class=\"p\">Click the\u00a0More Options\u00a0icon and select the\u00a0<strong>Batch Edit\u00a0<\/strong>option. Each column will now have an input field.<\/li>\n<li class=\"p\">Enter the value in the input field of each column for the fields that need to be updated.<\/li>\n<li class=\"p\">A green tick icon is shown against that column, click it to apply the changes to the selected task(s).<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-21835 size-full\" src=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Task-Batch-Edit.jpg\" alt=\"\" width=\"1363\" height=\"654\" srcset=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Task-Batch-Edit.jpg 1363w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Task-Batch-Edit-300x144.jpg 300w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Task-Batch-Edit-1024x491.jpg 1024w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Task-Batch-Edit-768x369.jpg 768w\" sizes=\"(max-width: 1363px) 100vw, 1363px\" \/><\/li>\n<\/ol>\n<h3><a id=\"FilteringTasks\"><\/a>Filtering Tasks<\/h3>\n<p>Column Filter helps to filter the list quickly based on the existing columns.<\/p>\n<p>The filtered task will always be shown with all its parent tasks. Mouse-hover on the column to be filtered and click the arrow to specify the conditions for filtering. In the Filter option menu, select one or more values. Click Apply. The list view now displays tasks with the filtered criteria.<\/p>\n<p>To remove all the applied filters and view all workitems, click the <strong>More Options<\/strong>\u00a0icon and select the\u00a0<strong>Remove Filter<\/strong> option.<\/p>\n<p><strong>Note: <\/strong><\/p>\n<ul>\n<li>The applied filter will persist within a session.<\/li>\n<li>Gantt Chart is disabled for filtered task plan.<\/li>\n<\/ul>\n<h3><a id=\"CompleteTasks\"><\/a>Complete Tasks<\/h3>\n<p>You can close tasks by disabling the Time-Entry for the tasks.<\/p>\n<p>To disable resources to enter time for tasks, click the\u00a0<strong>Close Task Assignment<\/strong> icon on the toolbar of the Task Assignment window, this closes the Time-Entry for that task. However, the task will continue to appear in the resource\u2019s timesheet and the timesheet cells will be grayed out.<a id=\"ReopenTask\"><\/a><\/p>\n<p>You can also disable Time-Entry for tasks by clicking the\u00a0<strong>Close<\/strong>\u00a0button at the bottom of the Detail view of the task.<\/p>\n<p>You can reopen the task i.e. timesheet entry for a closed task by clicking the \u2018Reopen Task\u2019 button available for closed tasks.<\/p>\n<h4><strong><a id=\"CopyTasks\"><\/a>Copy-Paste Tasks<\/strong><\/h4>\n<p data-start=\"184\" data-end=\"423\">To create tasks with the same planned dates, select the checkbox next to the task(s), then right-click and choose <strong data-start=\"298\" data-end=\"306\">Copy<\/strong>. When you paste the task using the right-click option, it is added at the same hierarchy level as the original task.<\/p>\n<p data-start=\"425\" data-end=\"507\"><strong data-start=\"425\" data-end=\"442\">Alternatively<\/strong>, you can copy and paste multiple tasks using keyboard shortcuts:<\/p>\n<ul>\n<li><strong data-start=\"510\" data-end=\"521\">Windows<\/strong>: <code data-start=\"523\" data-end=\"533\">Ctrl + C<\/code> to copy and <code data-start=\"546\" data-end=\"556\">Ctrl + V<\/code> to paste<\/li>\n<li><strong data-start=\"570\" data-end=\"583\">Mac (iOS)<\/strong>: <code data-start=\"585\" data-end=\"594\">Cmd + C<\/code> to copy and <code data-start=\"607\" data-end=\"616\">Cmd + V<\/code> to paste<\/li>\n<\/ul>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-21239 size-full\" src=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Add.png\" alt=\"\" width=\"852\" height=\"354\" srcset=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Add.png 852w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Add-300x125.png 300w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2023\/04\/Add-768x319.png 768w\" sizes=\"(max-width: 852px) 100vw, 852px\" \/><\/p>\n<h3><a id=\"Assign\"><\/a>Assign\/Unassign Resources to Tasks<\/h3>\n<p>To assign resources for a task, click the Resource cell for the respective task. Click the drop-down icon to open the Resources list.<\/p>\n<p>If the resources are already assigned, the team member is listed with the corresponding check box selected.<\/p>\n<p>To search team members, enter a search string such as part of the last name or first name, in the Search box. From the results displayed, select the checkboxes for the required team members and click the <b>Apply<\/b>\u00a0button.<\/p>\n<p><a href=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/assignment_panel-2.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-11125\" src=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/assignment_panel-2.jpg\" alt=\"\" width=\"353\" height=\"353\" srcset=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/assignment_panel-2.jpg 353w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/assignment_panel-2-300x300.jpg 300w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/assignment_panel-2-150x150.jpg 150w\" sizes=\"(max-width: 353px) 100vw, 353px\" \/><\/a><\/p>\n<p>The Task planned start and finish dates are copied to allocation dates when the allocation for a team member is added for the first time.<\/p>\n<p>When you assign a team member, he\/she will be assigned 100% by default for the Task duration.<\/p>\n<p>To unassign a team member from a task, simply clear their selection. If the team member has already logged time against the task, a warning will appear indicating that time has been posted.<\/p>\n<h3><a id=\"Hierarchies\"><\/a>Set the Hierarchy Level in the Task<\/h3>\n<p data-start=\"381\" data-end=\"740\">As your Task Plan grows with multiple tasks and subtasks, expanding and collapsing summary tasks individually can become time-consuming. The <strong data-start=\"522\" data-end=\"541\">Hierarchy Level<\/strong> option in the Task Plan view helps you control how deeply nested tasks are displayed. This makes it easier to scan the plan and understand the relationships between summary tasks and their subtasks.<\/p>\n<p data-start=\"742\" data-end=\"789\">To view tasks up to a specific hierarchy level:<\/p>\n<ol>\n<li data-start=\"793\" data-end=\"861\">From the top bar in the Task Plan, open the <strong data-start=\"837\" data-end=\"850\">All Tasks<\/strong> drop-down.<\/li>\n<li data-start=\"793\" data-end=\"861\">Select the desired <strong data-start=\"884\" data-end=\"903\">Hierarchy Level<\/strong>.<\/li>\n<\/ol>\n<p data-start=\"906\" data-end=\"1044\">Tasks beyond the selected level appear collapsed. You can expand a specific task to view its subtasks, and collapse it again to hide them.<\/p>\n<p data-start=\"1046\" data-end=\"1315\">The <strong data-start=\"1050\" data-end=\"1069\">Hierarchy Level<\/strong> list displays levels one less than the maximum hierarchy in the plan. For example, if your plan has tasks nested up to Level 6, the list shows options up to Level 5. To view all tasks regardless of depth, select <strong data-start=\"1282\" data-end=\"1295\">All Tasks<\/strong> from the drop-down.<\/p>\n<p data-start=\"1317\" data-end=\"1326\"><strong data-start=\"1317\" data-end=\"1326\">Note:<\/strong><\/p>\n<ul data-start=\"1327\" data-end=\"1564\">\n<li data-start=\"1327\" data-end=\"1564\">\n<p data-start=\"1329\" data-end=\"1564\">Indenting or outdenting tasks changes the task hierarchy, but does not dynamically update the values in the Hierarchy Level list.<br data-start=\"1458\" data-end=\"1461\" \/>For example, if you reduce your plan from Level 6 to Level 3, the list may still show levels up to 6.<\/p>\n<\/li>\n<\/ul>\n<div class=\"helpful-block-content wth-theme-thumbs\" data-title=\"\" >\n<ul>\n<li><span class=\"wth-title\">Was this helpful?<\/span><\/li>\n<li><a data-post=\"15607\" data-post-url=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/article\/getting-to-know-more-about-tasks-section-features\/\" data-post-title=\"Getting to Know More About Tasks Section Features\" data-response=\"1\" href=\"#\" class=\"wth-green-btn icon-thumbsup\">Yes<\/a>&nbsp; &nbsp;<a data-response=\"0\" data-post=\"15607\" data-post-url=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/article\/getting-to-know-more-about-tasks-section-features\/\" data-post-title=\"Getting to Know More About Tasks Section Features\" href=\"#\" class=\"wth-red-btn icon-thumbsdown\">No<\/a><\/li>\n<\/ul>\n<\/div>","protected":false},"author":1,"featured_media":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","multi-rating":{"mr_rating_results":[]},"_links":{"self":[{"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/article\/15607"}],"collection":[{"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/article"}],"about":[{"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/types\/article"}],"author":[{"embeddable":true,"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/comments?post=15607"}],"version-history":[{"count":32,"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/article\/15607\/revisions"}],"predecessor-version":[{"id":21836,"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/article\/15607\/revisions\/21836"}],"wp:attachment":[{"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/media?parent=15607"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}