Once turned off, the movement between iterations never results in a task period update.
Once turned on, the task period is adjusted to iteration's period if a user performs an action on the Board. A movement between iterations which is an effect of a movement between matched Jira sprints (Small or Large Team Synchronization Mode) will not result in the task period update until you set it accordingly (read more: Updating the task period as an effect of changes in Jira Sprints).
If task's End Date is outside iteration period, that task's assignment is considered as incorrect. It is indicated by the red calendar on the task card (visible only when Warnings are enabled).
A special dialog box appears whenever the user clicks on the red calendar info. User can choose between two ways of resolving such a conflict:
You are provided with two strategies of adjustment task period. The first strategy called "precise alignment" assumes, that you work in a fully agile manner and task duration is not significant as long as the team declares to complete the task within an iteration. Once you check that option, the application will always align task dates (start and end dates) with iteration dates by synching task period.
BEFORE THE ADJUSTMENT
Task period before the adjustment does not influence the result of the adjustment.
AFTER THE ADJUSTMENT
The second adjustment strategy called "smart adjustment" assumes that base task duration is intended. It means that application adjusts start and/or end date of the task so that they are always in-between iteration period, but it tries to avoid changing task duration. Take a glance at the following scenarios to understand how it works and select that option if you wish to take advantage of that algorithm.
1) Whole task period is contained in the iteration period → do nothing.
2) Whole task period is located before the iteration period (Task period is not longer than an iteration period) → task will be moved to start at the beginning of the iteration and the period length will remain unchanged.
3) Whole task period is after the iteration period (Task period is not longer than iteration period) → task will be moved to end at the end of the iteration, period length will remain unchanged.
4) Whole task period is located before the iteration period (Task period is longer than the iteration period) → task will be moved to start at the beginning of the iteration and end at the end of the iteration.
Under some circumstances, Gantt's Task Mode may be shifted whenever changes are made in the Board module. For example whenever we choose Data -> Task Mode -> Auto, it appears to work as intended. But then whenever we move a Parent to another iteration on the Board - Subtasks do not stay within the Start and End Date of the Parent. Also if you look at the Subtask's Task Mode you will notice that the system automatically changes it back to the Manual instead of keeping it in the Auto setting.
Updating the task period as an effect of changes in Jira Sprints
Once you turn on 'Task period synchronization', you are allowed to decide whether you want update task period based on changes performed out of BigPicture (eg. by modifying value of "Sprint" field on issue detail page).
It means, that when you check an option 'Synchronize with Jira changes', every movement of the task between Sprints in Jira (in Small or Large Team Synchronization Mode) results in the task period update (in line with the rules mentioned above).
Visualization of iterations on the Gantt chart
Please keep in mind that moving tasks on the Gantt chart will never move tasks between iterations on the Board only if "Task period synchronization" is enabled. Iterations . iterations on the Gantt are only a visualization which will help you in matching Iteration dates with Gantt timelineand not the drop area.
Board uses the same linking system as Gantt does. Therefore, whenever one creates a link on the Board, it will be automatically visible on the Gantt chart and vice versa.
Modules in our app are parts of a bigger project portfolio management powerhouse. Therefore they are must be integrated in many aspects. The purpose of this documentation piece is here to explain in which way our Gantt module synchronizes with the Board.
Please keep in mind that moving tasks on the