Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Current »

To view the general preferences, ensure that you have administrator rights in JIRA and that you can access the administrative menus.

Beside configuring a Checklist through its definition, you also have preferences that apply to all the Checklists. You can find such global preferences under Settings > Add-ons > General Preferences.

The available preferences are:

Display checklists in Issue Details section

By default, Checklists are displayed on the right-side panel of an issue. However, if you want to view the Checklists directly in the issue details, you must enable this preference. If you do so, the system displays the Checklists section below the Description section in the Issue Details section.

Display checklists under tabs

By default, when multiple Checklists exist in the same issue, the system displays all such Checklists on top of each other. To get each Checklist displayed under a tab, you must enable this preference. Thus, you can save vertical real estate.

You can chose to individually control how the Checklists are displayed in the issue view and in the agile boards.

Do not update global items for closed issues

By default, checklists have always their global items synced. To prevent the update when the issue is closed, you must enable this preference.

Increased Loading Time

If this feature is enabled, the add-on will have to check an issue status each time before loading. This can increase the add-on loading time up to a few seconds for each issue that you open. 

Hide add-on from projects not impacted by Definitions

By default, projects not affected by any Checklist Definition will not display the checklist panel. To display the panel in every project, you must disable this preference.

If any of your Checklist Definitions' Context is for All Projects, then the add-on will be displayed no matter if the context is only for specific issue types. 

  • No labels