{"id":6224,"date":"2022-03-08T10:46:59","date_gmt":"2022-03-08T10:46:59","guid":{"rendered":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/?post_type=article&#038;p=6224"},"modified":"2023-08-31T07:02:57","modified_gmt":"2023-08-31T07:02:57","slug":"how-to-sync-calendar-for-all-tasks","status":"publish","type":"article","link":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/article\/how-to-sync-calendar-for-all-tasks\/","title":{"rendered":"How to Sync Calendar for all Tasks"},"content":{"rendered":"<h2>Overview<\/h2>\n<p>At times, resources may need to change their working hours or add non-working days to their calendar. For this change to reflect the task&#8217;s duration and planned effort of the resource, the project managers can edit one of the relevant task fields such as Planned Start, Planned Finish, Planned Effort, or Percent Allocation of each task on which the resource was assigned. However, if there are several such tasks that need to be revised Planned Effort and Duration, the Sync Calendar feature comes in handy. This feature recomputes the Planned Effort and the Planned Duration for all Open Tasks and Open Assignments in one go.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-8037 size-full\" src=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/Sync_calendar.jpg\" alt=\"\" width=\"845\" height=\"427\" srcset=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/Sync_calendar.jpg 845w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/Sync_calendar-300x152.jpg 300w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/Sync_calendar-768x388.jpg 768w\" sizes=\"(max-width: 845px) 100vw, 845px\" \/><\/p>\n<h2>Working on Sync Calendar<\/h2>\n<p>The Sync Calendar option is available only when the Simple Scheduling Task plan status is Checked In. For the computation of Planned Effort, the calendar for reference is the resource calendar.<\/p>\n<p>As and when the changes happen the project manager needs to go to the respective task plan and decide to Sync the Calendar accordingly. On hovering over the Sync Calendar icon, shows the last date &amp; time on which the sync was performed. For example, the <b>Calendar last synced on 14-May-2020 at 16:58:02<\/b>.<\/p>\n<p>For a better understanding of how the Sync Calendar works, we have covered a few scenarios considering the following update in the planned task by a Project Manager.<\/p>\n<p class=\"whs2\"><strong>Resource Calendar in the following table is referred for Planned Effort computation.<\/strong><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-7995 size-full\" src=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C1.jpg\" alt=\"\" width=\"444\" height=\"61\" srcset=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C1.jpg 444w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C1-300x41.jpg 300w\" sizes=\"(max-width: 444px) 100vw, 444px\" \/><\/p>\n<p><strong>Project Calendar in the following table is referred for Planned Duration computation.<\/strong><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-7996 size-full\" src=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C2.jpg\" alt=\"\" width=\"444\" height=\"41\" srcset=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C2.jpg 444w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C2-300x28.jpg 300w\" sizes=\"(max-width: 444px) 100vw, 444px\" \/><\/p>\n<p><b>Scenario 1<\/b>: When your Task Plan Dates fall under the Non-Working Days<\/p>\n<ol class=\"whs5\" type=\"a\">\n<li class=\"p\">Consider you have one resource (<b>Res1<\/b>) and the status of your work is\u00a0<b>Open<\/b>\u00a0having\u00a0<b>one open Assignment<\/b>.<\/li>\n<\/ol>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-8006 size-full\" src=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C3.jpg\" alt=\"\" width=\"554\" height=\"93\" srcset=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C3.jpg 554w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C3-300x50.jpg 300w\" sizes=\"(max-width: 554px) 100vw, 554px\" \/><\/p>\n<p><b>Results<\/b>:<\/p>\n<ul class=\"whs8\" type=\"disc\">\n<li class=\"p\">Planned Effort gets updated as per the updated working hours (<b>9 hrs.<\/b>) and updated count of working days (<b>3 working days<\/b>) and also gets rolled up at the task level as per the Resource Calendar working hours.<\/li>\n<li class=\"p\">Planned Duration gets updated as per the updated count of working days at the task level as per the Project Calendar working hours.<\/li>\n<li class=\"p\">Since there is only one assignment, the planned effort and duration are the same.<\/li>\n<\/ul>\n<ol class=\"whs5\" start=\"2\" type=\"a\">\n<li class=\"p\">Consider an open task having two resources and one resource (<b>Res1<\/b>) has the status of an assignment as\u00a0<b>Closed<\/b>, whereas another resource (<b>Res2<\/b>) has the status of an assignment as\u00a0<b>Open<\/b>.<\/li>\n<\/ol>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-8007 size-full\" src=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C4.jpg\" alt=\"\" width=\"556\" height=\"111\" srcset=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C4.jpg 556w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C4-300x60.jpg 300w\" sizes=\"(max-width: 556px) 100vw, 556px\" \/><\/p>\n<p><b>Results<\/b>:<\/p>\n<ul class=\"whs8\" type=\"disc\">\n<li class=\"p\">Calendar changes impact only the open task assignments of an open task.<\/li>\n<li class=\"p\">The closed task assignment remains untouched and unaffected by the calendar changes.<\/li>\n<li class=\"p\">The Planned Effort gets recomputed for open task assignments (updated working hours i.e., <b>9 hrs.<\/b> \u00d7 updated working days after removing two non-working days i.e.,\u00a0<b>3 working days<\/b>\u00a0=\u00a0<b>27 hrs.<\/b>) \u00a0and rolled up at the task level as per the Resource Calendar working hours.<\/li>\n<li class=\"p\">The Planned Duration gets recomputed for the task to adhere to the number of working days as per the Project Calendar working hours.<\/li>\n<\/ul>\n<ol class=\"whs5\" start=\"3\" type=\"a\">\n<li class=\"p\">Consider an open task having two resources and both resources (<b>Res1<\/b>\u00a0and\u00a0<b>Res2<\/b>) have the status of their assignments as\u00a0<b>Open<\/b>.<\/li>\n<\/ol>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-8008 size-full\" src=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C5.jpg\" alt=\"\" width=\"555\" height=\"110\" srcset=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C5.jpg 555w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C5-300x59.jpg 300w\" sizes=\"(max-width: 555px) 100vw, 555px\" \/><\/p>\n<p><b>Results<\/b>:<\/p>\n<ul class=\"whs8\" type=\"disc\">\n<li class=\"p\">Calendar changes impact both the open task assignments of the open task.<\/li>\n<li class=\"p\">The Planned Effort gets recomputed (updated working hours i.e., <b>9 hrs.<\/b> \u00d7 updated working days after removing two non-working days i.e.,\u00a0<b>3 working days = 27 hrs. per resource<\/b>) for open task assignments and rolled up at the task level as per the Resource Calendar working hours.<\/li>\n<li class=\"p\">The Planned Duration gets recomputed for the task to adhere to the number of working days as per the Project Calendar working hours.<\/li>\n<\/ul>\n<ol class=\"whs5\" start=\"4\" type=\"a\">\n<li class=\"p\">Consider you have one resource (<b>Res1<\/b>) and the status of your work is\u00a0<b>Closed<\/b>.<\/li>\n<\/ol>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-8010 size-full\" src=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C6.jpg\" alt=\"\" width=\"556\" height=\"91\" srcset=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C6.jpg 556w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C6-300x49.jpg 300w\" sizes=\"(max-width: 556px) 100vw, 556px\" \/><\/p>\n<p class=\"whs7\"><b>Result<\/b>: No changes happen to any task details as a closed task cannot be changed.<\/p>\n<p class=\"whs12\"><b>Scenario 2<\/b>: When your Task Plan Dates fall before the Non-Working Days<\/p>\n<ol class=\"whs5\" type=\"a\">\n<li class=\"p\">Consider you have one resource (<b>Res1<\/b>) and the status of your work is\u00a0<b>Open<\/b>\u00a0having\u00a0<b>one open Assignment<\/b>.<\/li>\n<\/ol>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-8011 size-full\" src=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C7.jpg\" alt=\"\" width=\"556\" height=\"90\" srcset=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C7.jpg 556w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C7-300x49.jpg 300w\" sizes=\"(max-width: 556px) 100vw, 556px\" \/><\/p>\n<p><b>Results<\/b>:<\/p>\n<ul class=\"whs8\" type=\"disc\">\n<li class=\"p\">Planned Effort under\u00a0<b>After<\/b>\u00a0column as highlighted gets updated as per the new working hours (<b>9 hrs.<\/b>) and also gets rolled up at task level as per the Resource Calendar working hours.<\/li>\n<li class=\"p\">Planned Duration gets updated as per the new working hours (<b>9 hrs.<\/b>) between the task dates as per the Project Calendar working hours.<\/li>\n<li class=\"p\">Since there is only one assignment, the planned effort and duration are the same.<\/li>\n<\/ul>\n<ol class=\"whs5\" start=\"2\" type=\"a\">\n<li class=\"p\">Consider an open task having two resources and one resource (<b>Res1<\/b>) has the status of an assignment as\u00a0<b>Closed<\/b>, whereas another resource (<b>Res2<\/b>) has the status of an assignment as\u00a0<b>Open<\/b>.<\/li>\n<\/ol>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-8012 size-full\" src=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C8.jpg\" alt=\"\" width=\"554\" height=\"109\" srcset=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C8.jpg 554w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C8-300x59.jpg 300w\" sizes=\"(max-width: 554px) 100vw, 554px\" \/><\/p>\n<p><b>Results<\/b>:<\/p>\n<ul class=\"whs8\" type=\"disc\">\n<li class=\"p\">Calendar changes impact only the open task assignments of an open task.<\/li>\n<li class=\"p\">The closed task assignment remains untouched and unaffected by the calendar changes.<\/li>\n<li class=\"p\">The Planned Effort gets recomputed for open task assignments as per updated working hours (<b>9 hrs.<\/b>) and rolled up at the task level as per the Resource Calendar working hours.<\/li>\n<li class=\"p\">The Planned Duration gets recomputed as per the new working hours (<b>9 hrs.<\/b>) between the task dates as per the Project Calendar working hours.<\/li>\n<\/ul>\n<ol class=\"whs5\" start=\"3\" type=\"a\">\n<li class=\"p\">Consider an open task having two resources and both resources (<b>Res1<\/b>\u00a0and\u00a0<b>Res2<\/b>) have the status of their assignments as\u00a0<b>Open<\/b>.<\/li>\n<\/ol>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-8014 size-full\" src=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C9.jpg\" alt=\"\" width=\"538\" height=\"111\" srcset=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C9.jpg 538w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C9-300x62.jpg 300w\" sizes=\"(max-width: 538px) 100vw, 538px\" \/><\/p>\n<p><b>Results<\/b>:<\/p>\n<ul class=\"whs8\" type=\"disc\">\n<li class=\"p\">Calendar changes impact both the open task assignments of the open task.<\/li>\n<li class=\"p\">The Planned Effort gets recomputed for open task assignments as per updated working hours (<b>9 hrs.<\/b>) \u00a0and rolled up at the task level as per the Resource Calendar working hours.<\/li>\n<li class=\"p\">The Planned Duration gets recomputed for the task to adhere to the number of working days as per the Project Calendar working hours.<\/li>\n<\/ul>\n<ol class=\"whs5\" start=\"4\" type=\"a\">\n<li class=\"p\">Consider you have one resource (<b>Res1<\/b>) and the status of your work is\u00a0<b>Closed<\/b>.<\/li>\n<\/ol>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-8034 size-full\" src=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C10-1.jpg\" alt=\"\" width=\"554\" height=\"92\" srcset=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C10-1.jpg 554w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C10-1-300x50.jpg 300w\" sizes=\"(max-width: 554px) 100vw, 554px\" \/><\/p>\n<p class=\"whs7\"><b>Result<\/b>: No changes happen to any task details as a closed task cannot be changed.<\/p>\n<p class=\"whs12\"><b>Scenario 3<\/b>: When your Task Plan Dates fall after the Non-Working Days<\/p>\n<p class=\"whs7\"><b>Result<\/b>: The behavior will be the same as that of\u00a0<b>Scenario 2<\/b>\u00a0where tasks were before the Non-working days.<\/p>\n<p class=\"whs12\"><b>Scenario 4<\/b>: Summary Level Task Behavior<\/p>\n<ol class=\"whs5\" type=\"a\">\n<li class=\"p\">The Planned Effort of summary tasks is the sum of all its child tasks.<\/li>\n<li class=\"p\">The Planned Duration continues to be computed based on the number of working days between the summary task\u2019s planned start and end date and working hours as per the calendar.<br \/>\nFor example: Consider a summary level task with one child task closed and another open.<br \/>\nBased on the non-working days added on\u00a0<b>8th<\/b>\u00a0&amp;\u00a0<b>9th Jan 2020<\/b>\u00a0and updated working hours (<b>9 hrs.<\/b>)<\/li>\n<\/ol>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-8035 size-full\" src=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C11.jpg\" alt=\"\" width=\"609\" height=\"110\" srcset=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C11.jpg 609w, https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/C11-300x54.jpg 300w\" sizes=\"(max-width: 609px) 100vw, 609px\" \/><\/p>\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=\"6224\" data-post-url=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/article\/how-to-sync-calendar-for-all-tasks\/\" data-post-title=\"How to Sync Calendar for all Tasks\" data-response=\"1\" href=\"#\" class=\"wth-green-btn icon-thumbsup\">Yes<\/a>&nbsp; &nbsp;<a data-response=\"0\" data-post=\"6224\" data-post-url=\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/article\/how-to-sync-calendar-for-all-tasks\/\" data-post-title=\"How to Sync Calendar for all Tasks\" 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\/6224"}],"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=6224"}],"version-history":[{"count":16,"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/article\/6224\/revisions"}],"predecessor-version":[{"id":16880,"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/article\/6224\/revisions\/16880"}],"wp:attachment":[{"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/media?parent=6224"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}