It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Why BigPicture is not properly syncing issue updates in Jira?

We have setuped BigPicture to track the progress of our projects by Epic level and so far it's working fine. But sometimes when we move issues from one Epic to another those chages are not reflected in BigPicture Gantt. 
Clicking the manual Re-Sync works sometimes but it also fail to update the Gantt chart sometimes. In order to get it to sync we have reconfigure the progran and sync again.
Could you please help me to figure out the reason for this? Is there's a place we can configure a sync interval? Couldn't find much details about sync configurations in the documentation
This is the configurations for the program we are having this issue.

Screenshot_2018-10-05 Program configuration - JIRA.png

3 answers

Hi Isuru,

In your case there are two things to consider. First is Synchronizers versus Manual Changes on WBS.

As I am sure you know Synchronizers build your WBS structure automatically. They work in the following way:

Since your configuration has "Synchronize Project Structure" on top than this is checked first. If any task is not under its project than it is indented under the correct Project. Then the next(in your case Epc Synchronizer) is executed and it moves all the tasks under their epics accordingly. Your last synchronizer ("Synchronize Subtasks") is the last and it in turn indents any subtasks under it's parent task. That is how the automatic WBS structure is built.

The reason why your manual  changes do not persist is connected with the second issue at hand here, namely: the fact that our plugin does not automatically update changes to Epic links. We have not implemented this feature yet although it is one of our top priorities currently.

While you move tasks under different Epic the Epic Link is not updated unfortunately and after the re-sync the syncronizers indent it back under it's Epic. That is why you need to rebuild the structure to make the changes persist.

A word of advice here. If you want to make manual changes it is probably a good idea to remove sychronizers altogether and just stick to manual changes. That way the manual changes will not be reverted back by the automatic synchronizers.

Should you need more explanation regarding this matter please remember you can always contact us at We are always more than happy to help.

Do you have any update on this feature (i.e. sync/update Epic Name "back" to Jira issue)?

I'm asking becauze we're having the exact same problem, but with the fixVersion field...

  1. initially setting fixVersion in byediting Jira issue
  2. updating/sync gantt to see correct parrent/child relationship (this works)
  3. manually moving epics from one version to another in gantt
  4. fixVersion field is NOT updated in jira

When will this change? It is annoying to constantly hear from Atlassian/Softwareplant that features will be released soon but you never hear anything later. Disappointing. 

We really need this feature.

Same here, Im using big gantt cloud and it doesnt re sync properly when creating issues after the creation of the program... it just doesnt load any new issue.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Jira Cloud for Google Sheets: Automatically Refresh Your Data!

Remember that time you realized it was possible to refresh your Jira data in Google sheets with just one click? What if we told you that you can now get the latest data with no clicks at all?! Zero! ...

7,369 views 33 29
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you