...
The following table shows the propagation delay times for the following operations (based on the times of the cache refresh in Jira Cloud):
Change type | Delay time | Change visible to users |
|---|---|---|
installing or uninstalling Jira Software | up to 10 minutes | |
change of license | up to 15 minutes | |
adding, removing, or editing a component | up to 1 hour | after Box synchronization or task modification |
adding, removing, or editing a Custom Field | up to 15 minutes | |
adding, removing, or editing a filter | up to 1 hour | after Box synchronization forced manually |
adding, removing, or editing a link type | up to 1 hour | |
adding, removing, or editing an issue type | up to 1 hour | |
adding, removing, or editing an issue status | up to 1 hour | after Box synchronization or task modification |
adding, removing, or editing a workflow | up to 1 hour | |
adding, removing, or editing a workflow scheme | up to 1 hour | |
adding, removing, or editing a group or its members | up to 1 hour | |
adding, removing, or editing a priority | up to 1 hour |
| Info |
|---|
The times presented concern the propagation of status values being cached after a change. Clicking the “Clear Cache" button invalidates the plugin cache, which forces a complete data reload from the Jira database for all boxes and all users (full recalculation of all the program boxes similar to recreating the programs from scratch). Depending on the volume of data in your Jira, it can take up to several minutes to execute while the application will not allow data editing during that time. Use it with caution as it will influence server performance and users' ability to work with the application.
|
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:
...