Changes made in Jira may be visible in BigPicture, BigGantt, and BigTemplate with some delay, depending on the delay of the refresh mechanism for data stored in the cache.

To speed up the propagation of changes, you may proceed to a cache cleanup but, in the case of large data sets, this can cause your plugin to stop working for the resynchronization time.


Propagation of changes with a delay

The following table shows the propagation delay times for the following operations performed in Jira:

Change type

From version 8.2.x

Older versions

installing or uninstalling Jira Software

up to 10 minutes

up to 1 hour

change of license

up to 15 minutes

up to 1 hour

adding, removing, or editing a component

up to 1 hour

up to 1 hour

adding, removing, or editing a Custom Field

up to 1 hour

up to 1 hour

adding, removing, or editing a filter

up to 1 hour

up to 1 hour

adding, removing, or editing a link type

up to 1 hour

up to 1 hour

adding, removing, or editing an issue type

up to 1 hour

up to 1 hour

adding, removing, or editing an issue status

up to 1 hour

up to 1 hour

adding, removing, or editing a workflow 

up to 1 hour

up to 1 hour

adding, removing, or editing a workflow scheme

up to 1 hour

up to 1 hour

adding, removing, or editing a group or its members

up to 1 hour

up to 1 hour

Propagation of changes without any delay

When you update information related to issues or projects in Jira, such changes should be reflected in BigPicture, BigGantt, and BigTemplate in real-time.

The following screenshots present the operations updated without any delay: