Respect Jira screen scheme
This functionality is available only in the Server version of the App. The following section doesn't apply to cloud users - the screen scheme is always automatically respected in the cloud version of the App. More information on the differences between cloud and server versions of the App can be found here.
The "Respect Jira screen scheme" toggle switch applies to start/end date field mapping.
Bi-directional sync:
App → Jira
When you move a task on the Gantt chart, → you change the start/end date of a task → you change the values of the mapped fields.
If "End date" is mapped to "Due date," → changing the "End date" on the Gantt chart → changes the value of the "Due date" field in Jira.
Jira → App
When you update a field in Jira, → you change the start/end date of a task → you move the task on the Gantt timeline.
If "End date" is mapped to "Due date," → changing the "Due date" in Jira → changes the value of the "End date" on the Gantt timeline.
Remember, both "Start date" and "End date" can reflect a selected Jira field.
For example, "End date" can be mapped as "Due date."
Toggle switch off:
Bi-directional sync (of start/end date) is not required but will be performed when possible.
Even when fields mapped as start/end date cannot be updated by the App (because they haven't been added to the project's Jira screen scheme), you can still freely move tasks on the Gantt chart, etc. - even though a Jira field cannot reflect those changes, you still can make them in the App. The bi-directional sync isn't required - it's performed when possible, but when it can't be done, the App still lets you change the start/end date.
The toggle switch on:
Bi-directional sync (of start/end date) is required. When the toggle switch is on, the App lets you change the start/end date of a task only if reflected in Jira.
This toggle switch will NOT stop the App from updating Jira values. It only prevents you from changing the start/end date in the App when it cannot be properly reflected in Jira.
When fields mapped as start/end date cannot be updated by the App (because they haven't been added to the project's Jira screen scheme), you can't change the start/end date in the App. If a field doesn't exist in your Jira project, the App cannot perform bi-directional sync and blocks you from changing the start/end date. You can't move a task on the Gantt timeline because the App can't update Jira field values to reflect start/end date changes.
When setup is complete (the fields selected for start/end date mapping exist in a Jira project), the App can perform bi-directional sync without problems. The fields mapped as start/end dates are updated accordingly.
Exception: Time Spent + Remaining Estimate and Original estimate
Time Tracking can be used for start/end date mapping, but the expected behavior is different.
Affects
The "Respect Jira screen scheme" toggle switch applies to start/end date field mapping.
Save task updates as comments
You can add task updates made using the App as Jira comments. Depending on your Jira settings, users can get notifications when a task is updated via the App.
Working with the Gantt module may update multiple dependent tasks with a single operation, which will result in numerous notifications if this option is enabled.
Such updates may also occur when the scope of the box is defined.
.png?version=1&modificationDate=1727442578535&cacheVersion=1&api=v2&width=895&height=400)
Send "Issue updated" notification after task updates
When enabled, the "Issue Updated" notification will be sent to users unless the users do not have the permissions to send notifications.
If notifications are not configured while this feature is enabled, only admin users will get notified.
Auto recalculation based on the assignee's working days
If a task is assigned to an individual resource, its period will always be automatically calculated based on the assignee’s working days, and the default Working schedule is ignored.
To learn more about absence days, go to Assigning Resources.
