---
title: "Global User Settings"
canonical: "https://support.55degrees.se/space/SP/3928686605/Global%20User%20Settings"
format: markdown
---
The Global User Settings are configurable items that affect the app as a whole and they are located under the **Settings** ⚙️ icon in the top right of the apps navigation bar in ActionableAgile® Analytics.
> ℹ️ For our Standalone version, you *first* need to click the Account Settings button (your initial letter), to be presented with the **Settings** cogwheel ⚙️.
> Macro (refined-tabs)
>
> > Macro (refined-tab)
>
> [JIra CLoud] [Azure DevOps] [Standalone]
>
> If you give your consent, we’ll use cookies and gather the necessary personal data to understand how you use the app so we can make meaningful improvements.
>
> This means that we gather information about your activities in the app, e.g. which features are used, the order in which features are used, etc.
>
> We use a **pseudonymized** version of your account ID and details about your device/browser to distinguish your actions from other users.
>
> We won't try to identify anyone personally. Our goal is only to separate user data to understand usage patterns and friction points for a user in general.
>
> It is **voluntary** to consent. If you consent, please note that you can withdraw your consent under settings in the app, at any time.
>
> Read more in our [cookie policy](https://www.55degrees.se/legal/app-cookie-policy) and our [privacy policy](https://www.55degrees.se/legal/privacy).
>
> |  |  |  |
> | --- | --- | --- |
>
>
> > Macro (refined-tab)
>
> [JIra CLoud & Data center] [Azure DevOps] [Standalone]
>
> Choosing this option deletes all of your settings and data that are saved in your browser. This is the "nuclear option" and means you'll need to reconfigure your workflows and settings again the next time you use the tool. As of now, there is no notification once you've clicked on this link but the action has happened behind the scenes!
>
> |  |  |  |
> | --- | --- | --- |
>
>
> > Macro (refined-tab)
>
> [JIra CLoud & Data center] [Azure DevOps] [Standalone]
>
> Use this setting to determine the date format that ActionableAgile should use when displaying your date-related data.
>
> |  |  |  |
> | --- | --- | --- |
>
>
> > Macro (refined-tab)
>
> [Azure DevOps] [Standalone]
>
> Choose which day starts your week.
>
> | |  |  |
> | --- | --- | --- |
>
> > Macro (refined-tab)
>
> [JIra CLoud & Data center] [Azure DevOps] [Standalone]
>
> You can choose between English and French.
>
> |  |  |  |
> | --- | --- | --- |
>
> > Macro (refined-tab)
>
> [Azure DevOps] [Standalone]
>
> You can choose which color scheme you want to use: [light] or [dark] mode.
>
> > ℹ️ Let there be light! In Jira, this setting is part of your native settings which can be toggled on and off under your Profile → Theme.
>
> |  |  |
> | --- | --- |
>
> > Macro (refined-tab)
>
> [JIra CLoud & Data center] [Azure DevOps] [Standalone]
>
> When opening ActionableAgile® Analytics, the Landing Page will be the first thing you see. If you prefer to have Example Data, the Last Loaded Data Set or a specific chart, you can change this in the settings.
>
> Just go to the ⚙️ icon in the top right, and continue according to the table.
>
> > ℹ️ Read more about the Landing page [here](https://55degrees.atlassian.net/wiki/spaces/SP/pages/3925115630?xpis=eyJicmlkZ2UiOiJzbWFydExpbmtzIiwiaWQiOiIxNzg0MTE3MzMzODk2Iiwic291cmNlIjoiY29uZmx1ZW5jZSJ9).
>
> | | **None/ Landing Page** | **Last Data Loaded** | **Example Data** | **Default Chart** |
> | --- | --- | --- | --- | --- |
> | Jira | Opens on the Landing Page. | Opens on the last data set you loaded. | Loads to the Dashboard chart with Example Data. | |
> | Azure DevOps | Opens on the Landing Page. | Opens on the last data set you loaded. | Loads to the Dashboard chart with Example Data. | |
> | Standalone | | | | Loads the Example Data on the chart of your choosing. |
>
> |  |  |  |
> | --- | --- | --- |
>
>
> > Macro (refined-tab)
>
> [JIra Data Center]
>
> |  | **Disable Custom Fields**
This setting lets you turn off the ability to import custom fields for your user. You may want to use this if you have issues loading data due, as often this is caused by an excessive number of global custom fields in your Jira instance. This is a known performance hit for Jira and is well-documented by Atlassian. It manifests in our app because the search API calls take too long and time out, which causes your data not to load.
In Data Center, there is a built-in custom field optimizer that will help you improve your custom field configuration.
**Jira Thread Count**
You can have up to 1 - 5 threads running at one time to fetch data. If you are having performance issues, you can reduce the number of threads and see if this helps. The lower the number of threads you choose, the fewer concurrent calls it will make. This results in a longer overall loading time.
**Jira Thread Speed**
This setting lets you determine relatively how much sleep you want to have between calls if any. Our default is no sleep - aka “0”. You can choose from the following options: 0 (no sleep), 250 or 1000 (most sleep).
**Jira Fetch Limit**
This setting lets you determine, relatively, how many Jira issues should be fetched in one query. By default, we fetch 50. However, if your instance has high latency or you have unusually verbose data, reducing this number may keep calls from timing out and ActionableAgile® Analytics from hanging on the loading screen. Choose between 10, 25, or 50. |
> | --- | --- |
>
> > Macro (refined-tab)
>
> [Azure DevOps]
>
> |  | Choose a lower Historical Data Fetch Limit when you experience your data failing to load as it might be timing out. |
> | --- | --- |