Wrong End date used in BigGantt

[Sara Roig]

Hi everyone!

I'm using BigGantt but I think there's a problem with the calculating of the Due Date and I don't know how to fix it...

This is how my General configuration is set: (I also tried with End date field: "Due Date" but I had some problems too)

The thing is that I have this Epic, and I changed the start date to 24/08/2020 in the Gantt (manually moving it), so automatically the due date is on 27/08/2020

But even though I Re-Sync when I go to the Epic it shows up like this, the due date is  still the old one, like it hasn't been refreshed...

And with the document (CSS-229) it has wrong start date and due date. (This document is a child of the epic and I think that there's something wrong configured with the documents because when I change the original estimate it is not modified in the Gantt and vice-versa)

It's like my fields are not well connected to the Gantt...

Does anybody know how can I fix it please?

Thank you a lot!

[Marcin Geb _SoftwarePlant_ · Accepted solution]

Hello Sara

Thanks for the interesting question. I investigated the issue a little bit and I think the Due date will not normally get updated automatically based on your Original Estimate. I found tips by the Community that you need a plugin for that. Without such plugin, the Due date is independent of the Start date + Original estimate. The two simply don't keep in sync.

And so you can elect whether tasks' bars will position themselves on the timeline of the Gantt chart based on the Due date or the Start date + Original estimate, as seen in figure 1.

Fig. 1

[Marcin Geb _SoftwarePlant_]

As for the CSS-229 "document" issue, I assume that's a custom issue type that you or a Jira admin at your organization have created. And so I created a custom 'Document' issue type on my own Jira instance, see below figure, but it works as expected -- the start date gets updated when I drag and drop the document's bar on the Gantt chart, with the original estimate untouched.

I'm far from claiming that an issue doesn't exist, I just need more details. What do you think? Is your configuration as pictured below?

[Sara Roig]

Hello Marcin! Thanks a lot for your help!

About the due date, ok I'm not so worried about this because I can keep working only using the start date and the original estimate. Anyways, do you know which is the name of that plugging? 

About the document issue, the original estimate and the start date are correct in the Gantt but not in the issue. I want it to be reflected on the issue because I'll be making clones of this Gantt to another projects and I need those fields to be correct. 
I'll show you a more detailed view of my problem.

This is my Gantt:

Now I move the Epic to a week after and I Re-Sync, here the document start date seems correct

But when I go to the issue I see  that the start date hasn't been refreshed (it should be 2020/08/27)

And the same happens with the Original Estimate (I had 3 days at first but I changed it in the Gantt for 1 day). Also I tried to change the original estimate in the issue but even though I Re-Sync the Gantt it wasn't reflected there either...

But notice that if the issue type is a Task it works correctly (the start date is the same as in the Gantt)

I don't know if this information is enough but if you need me to show you something else tell me.

Thanks for your time!! 

[Marcin Geb _SoftwarePlant_]

Hello Sara

As for the plugin capable of syncing the start date + original estimate with the due date, I'm not an expert; please accept this link.

As for your 'document' custom issue type, I raised a ticket with our support team; they are aware of this thread. I would consider this a bug. If nobody helps and the issue is not painful, I'd wait for the BigPicture version 8, which will debut shortly with the entirely redesigned Gantt chart, and I'd expect to have the issue fixed there.

[Marcin Geb _SoftwarePlant_]

This is how the support team resolved the issue:

(...) as the 'Timetracking' field is not enabled in your Jira project, BigPicture is not able to overwrite it. Hence, it re-synchs the tasks with the original values and, eventually, the tasks are rescheduled to their initial period.

Please follow the guidelines in this wiki section in order to amend your field configuration. This should prevent the issue from reoccurring.

[Sara Roig]

Hi @Marcin Geb _SoftwarePlant_ 

thanks a lot for your help! At the end the problem was because the Schema of the Documents was missing some fields, I added them and now it works correctly!