Support for Atlassian Server Products (and apps like BigPicture) is ending in February 2024.

Are you planning a migration to Cloud? Make sure you don't lose your BigPicture data/configurations in the process. Check out this page for information on how to migrate BigPicture's data to Cloud. If you have any questions please email

Start/end date fields

Start/End date fields

These fields determine the start and end positions of the task on the timeline.

Overwrite Jira task data with data from the App

If you want to use a different field, it is possible to overwrite Jira task data with data from BigPicture. When you select a different field than the one currently used, you will be able to switch on the "Overwrite Jira task data with data from the App" option below.

This action is irreversible.

In general, there are three main strategies for task synchronization:

  • Not synchronized use this option if you do not want to update Jira issues while still being able to plan using the Gantt module. Changes to date estimates will not sync to Jira, which means that task start and end dates might differ from the estimates in Jira issues.
  • Two 'Date picker' (or 'Date time picker') fields - recommended when assignees work on multiple tasks simultaneously. 
  • One 'Date picker' (or 'Date time picker') field and a time estimate field (Original estimate or Time spent + Remaining estimate) recommended for working on one task at a time.

Fields mapped above as a start and end date will not be updated by the App if they are not defined in the Jira Project Screen scheme (excluding Time Spent + Remaining Estimate). In other words, for synchronization to work, you must make sure that the fields exist in Jira for a particular project.

If you need more details, take a look at the example:

 Click here to expand...

A separate custom configuration has been specified for the "OMEGA" Jira project. This ensures that other projects are not affected.

Create a Jira Screen that has those fields. You can copy an existing screen and modify it to make things easier. In the example, a copy was made and named "OMEGA."

Add a Screen scheme. The system will ask you what screen you want to associate it with.

Add an Issue type screen scheme.

You'll be taken to the following screen (click the name of the Screen Scheme).

Click the name of the screen.

Make sure that the fields you have set in the Technical configuration are listed. In this case, the "Start Date" field already exists, and the "Due date" needs to be added.

Go to the Jira Project settings and implement the new screen scheme.

Now the App will be able to synchronize with Jira - making changes within the App will update respective fields.

Scheduling impact

From the 8.15 version of BigPicture onwards. 

Start/end dates mapped to estimate fields

  • Start date
    • can be mapped to Original Estimate
  • End date
    • can be mapped to Original Estimate or 
    • Time Spent + Remaining Estimate

Note: Only one of the fields (either start or end date) can be mapped to an estimate. The other field must remain as a date field, such as the start/end date. 

Expected behavior 

You can update the following values:

  • star/end date 
  • task duration 
  • the estimate field 

Updates can be done by:

  • change of a field value, for example by editing a value in a column in BigPicture
  • adjustment of a task position and length on a Gantt chart 

New start/end value (inline editing or update of a field on Jira issue page)  

Behavior is the same regardless of mapping:

  • change of the start date results in a task being moved.
  • change of the end date results in a task being resized. The estimate field and task duration field reflect the change. The start date is unaffected. 

start date updatedTask movedstart date(tick)
  • start date = Original Estimate
  • end date = Original Estimate
  • end date = Time Spent + Remaining Estimate
end date(tick)
task duration(error) 
end date updatedTask resizedstart date(error) 
end date(tick)
task duration(tick)

New task duration OR estimate field value

Behavior depends on the mapping:

  • the date mapped to the estimate is adjusted


task duration updated


estimate value updated

Task resizedstart date(tick)
  • start date = Original Estimate
end date(error) 
task duration(tick)
start date(error) 
  • end date = Original Estimate
  • end date = Time Spent + Remaining Estimate
end date(tick)
task duration(tick)

Task position adjusted on the timeline

All fields are updated to reflect the task position on the timeline. 

Affected by

The "Respect Jira screen scheme" toggle switch applies to start/end date field mapping.