The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Start/End dates automatically jump to Monday when scheduled on weekends (Tempo & BigPicture)

Burim Dervishi
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 10, 2026


Hi everyone,

I am facing an issue where Jira automatically shifts issue start or end dates away from weekends.

The Problem:
Whenever I set a Start Date or Due/End Date for an issue on a Saturday or a Sunday, the date automatically jumps to the next working day (Monday).

What I have already configured:

Tempo Timesheets/Planner: Worklog and holiday calendars are configured to allow work on weekends.

BigPicture: The working days / schedule calendar is explicitly configured to include Saturday and Sunday as working days.

Despite these settings, dates continue to snap to Monday.

 

Questions:

Is there a global Jira setting, field configuration, or scheduling scheme (e.g., in BigPicture or Jira native fields) that overrides app-specific calendars?

Could a workflow post-function, automation rule, or specific sync setting between BigPicture and Jira fields be causing this behavior?

How can I force Jira / BigPicture to accept weekend dates without auto-shifting them?

Any insights or guidance on how to fix this would be greatly appreciated!

Thanks in advance for your help.

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Germán Morales
Community Champion
August 10, 2026

Hi @Burim Dervishi , welcome to the Atlassian Community!

This is likely being caused by BigPicture scheduling, not by a global Jira Data Center setting. Jira’s native Due Date field does not use the Tempo or BigPicture working calendars, while BigPicture can adjust tasks around non-working days and synchronize the resulting Start and End dates back to Jira.

Use one affected task to isolate the cause:

  • Confirm that the weekend-enabled BigPicture Workload Plan is actually assigned to the task’s assignee, and that no Holiday Plan or individual absence marks Saturday or Sunday as unavailable.
  • Temporarily change the task’s Scheduling mode to Manual, set the weekend date directly in Jira, and refresh the work item.
  • Check Activity → History to see whether the date was subsequently rewritten.

If the date remains in Manual mode, BigPicture auto-scheduling or the assignee’s calendar is the cause. Keep the task in Manual mode when weekend dates must be fixed, or correct the BigPicture Workload Plan. The Tempo calendar should be checked separately because it does not replace the calendar BigPicture applies to the task.

If the date still moves in Manual mode, review the Jira Automation audit log, workflow post-functions, listeners, and BigPicture’s Start/End field mapping. Jira only requires the Schedule Issues permission to edit the native Due Date; there is no documented native setting that forces weekend dates to Monday. If History points back to BigPicture, provide the app version, task mode, field mapping, and assigned Workload Plan through the BigPicture Marketplace support page.

TAGS
AUG Leaders

Atlassian Community Events