BigPicture updates custom fields even after it's already set

[Angelie Wanner]

We set our own custom date fields to be pulled into BigPicture instead of the default Start/End date fields via the custom synchronization settings in technical configuration page.

We've noticed that BigPicture has been updating these fields in our issues even if the dates have already been set. Also, every time we try to update the fields, BigPicture reverts it back to the dates to its dates. 

This is causing some problems as the dates do not reflect our actual dates. The dates that BigPicture is putting in don't seem to make sense either.

[Brian Spence · Accepted solution]

I am running an older version of BP, but feel your pain.

I believe the answer is on the program configuration page.  You have to ensure you DON'T have "Recalculate parents" checked.  Otherwise it will always update any parent ticket based on the child's date.  I believe that applies to when a ticket is indented under a parent task, not just natural parent/child relationships like Story / Sub Task.

The New Tasks Default Mode can also change the dates when a new task is added, including changing the parent's dates.  I always leave this set to Locked.

Next, in the Task Hierarchy section, I always lock parents in the sync hierarchy.  

Last - Keep in mind that an issue can be included in multiple programs, and so long as one user creates a program incorrectly, it can start updating thousands of dates automatically, and there's no easy way to recover.

I've talked with the vendor about this, and haven't really received confirmation that those actions cover all scenarios, but have found that it has helped.  

[Angelie Wanner]

Hi Brian, thanks for the feedback. We were able to figure out the issue. It had to deal with the Task Mode configuration. I initially had it set to Lock, but with this setting the Parent issue will always be updated based on the last child story. We changed it to Manual, as this will allow you to change the dates for any issue without it affecting any parent/child relationships. Making this change resolved our issue.