This page walks you through global settings you can make for your user. For the most part they are the same across all versions of Jira, however, Jira Server and Data Center have choices that give the user more granular control over data fetching as well. Continue reading for more.

Jump to:

• 1 Clear Browser Storage
• 2 Date Display
• 3 Language
• 4 Default Data Set
• 5 Color Scheme
• 6 Server Settings
  • 6.1 Disable Custom Fields
  • 6.2 Jira Thread Count
  • 6.3 Jira Thread Speed
  • 6.4 Jira Fetch Limit

 

Open

 

Clear Browser Storage

Choosing this option deletes all of your stored chart control settings but not your data sets. There is no notification once you've clicked on this link, but the action has happened behind the scenes!

Date Display

Use this setting to determine the date format that ActionableAgile should use when displaying your date-related data.

Open

Language

Default Data Set

Color Scheme

Server Settings

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 five 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.

You can choose between the following options: 1, 2, 3, 4, or 5

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:

• 1000 (most sleep between calls)

• 250 (least sleep between calls)

• 0 (no sleep between calls)

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 datax1, reducing this number may keep calls from timing out and ActionableAgile from hanging on the loading screen.

You can choose between 10, 25, or 50.