Updating Task Dates: How Shotgun Thinks

When updating Task dates in an API update() request, there is no specified order to the values that are passed in. In order to clarify how updates are handled by Shotgun when there are multiple fields provided, we're showing you how Shotgun thinks in the bullet points below:

• Set schedule fields (milestone, est_in_mins, start_date, due_date) after all other fields, because the Project and Task Assignees affect schedule calculations.

• If start_date and due_date are both set, then ignore est_in_mins (Duration) (est_in_mins can often be wrong since it's easy to calculate scheduling incorrectly).

• If both start_date and due_date are provided, set start_date before due_date.

• Set milestone before other schedule fields (because start_date, due_date, and duration get lost if milestone is not set to false first)

• If milestone is being set to True, ignore est_in_mins

• If milestone is set to True and start_date and due_date are also being set to conflicting values, raise an Exception.

• If due_date and est_in_mins are set together (without start_date), set due_date after est_in_mins (otherwise setting est_in_mins will change due_date after it is set).