User-specific browser settings not being stored for Agile Hive

User-specific browser settings not being stored for Agile Hive



Update July 2025

Starting with Agile Hive version 20250715-01, released in July 2025, we have addressed the issue outlined on this page. User-specific settings are now stored on your Jira Cloud site rather than in the browser's local storage.

As a result, company restrictions on browser local storage should no longer cause any problems within Agile Hive. This update also resolves the issue of onboarding tours reappearing after each browser reload. If you continue to experience similar issues, please don't hesitate to submit a support request.

Note: All user settings have been reset, but this does not impact your data in any way. It's similar to accessing Agile Hive from a new browser or device - only your personal settings have been refreshed. As a result, the onboarding tour will be displayed again.

Introduction

Agile Hive stores certain settings in the browser on a per-user basis. These include preferences such as whether the main sidebar is collapsed, whether the user prefers a compact view of issue cards, and whether the onboarding tour has been completed or skipped.

 

Problem

Users are repeatedly presented with the Agile Hive Onboarding Tour, even after completing or skipping it. Additionally, other user-specific settings reset to default each time they use Agile Hive.

 

Potential Causes

Users who have reported similar issues were often impacted by one of the following web browser preference settings listed below.

Clearing browser data upon closure

Most browsers allow data to be deleted upon closing a window.

These settings are typically found in the browser's privacy and security settings section.

Blocking third-party cookies / cross site tracking prevention

In addition to the management of browser data all major browsers offer some form of tracking prevention, or protection against tracking by third party cookies. Atlassian loads Apps from a Content Delivery Network (CDN), therefore Agile Hive is seen as a third party, since the CDN's URL differs from the one assigned to your Jira instance (usually akin to “[companyname].atlassian.net”).

As a result data stored in your browser by Agile Hive will be removed upon leaving the site or closing the browser, if you have these protections enabled.

We also tracked issues with the loading of issue type and project icons caused by very strict tracking protection.

Ad-Blockers / Content Blockers

Ad-blockers and tracking prevention plugins can disrupt the handling of third-party cookies, which Jira Cloud apps depend on from a browser's perspective.

Consequently, Agile Hive may not function correctly if it cannot store data locally.

Company / Group policies

If your company enforces specific security policies, any of the scenarios mentioned above may apply by default. This could also prevent Agile Hive from functioning properly, as it may be unable to store data locally.

 

Resolution

Regarding the various potential causes, please make sure to take a closer look into the respective problem category and locate the browser settings defining the behavior of your web browser.

Exception from clearing browser data upon closure

Ensure that your browser does not delete all locally stored user data upon closing. To prevent Agile Hive’s settings from being removed, consider adding exceptions for your Jira URL and, if necessary, the CDN URL.

For guidance on locating these settings, please refer to the links below:

To find the Agile Hive CDN URL for your site, check your browser’s developer console. In Chrome, this can be found under the ‘Application’ tab by navigating to ‘Local Storage’ or ‘Session Storage.’ Please note that the process may vary for other web browsers.

250219_AgileHive_FindCDNURL.png

Exception from blocking third-party cookies / cross site tracking prevention

Just as you can set exceptions to prevent browser data from being deleted upon closing, you can also add exceptions for blocking third-party cookies or cross-site tracking prevention. Adding exceptions for Jira Cloud, Agile Hive, and the CDN URL may help resolve the issue.

For more information please refer to the following documentation:

To find the Agile Hive installation URL for your specific Jira Cloud site, please refer to the explanation at User-specific browser settings not being stored for Agile Hive.

Exception for Ad-Blockers / Content Blockers

If you have strict blocking rules in place, adding exceptions for your Jira instance can help. In Safari, such plugins are referred to as “Content Blockers.”

For guidance on adding exceptions, please refer to the documentation of the ad-blocker plugin you are using.

Checking Company / Group policies

If your company enforces specific browser settings and security policies, please contact your internal IT department for assistance in reviewing potential issues and adjusting the policies to ensure Agile Hive functions properly.

For details on policies affecting your browser, please refer to the relevant documentation below: