You need administrator rights in Jira to perform the tasks on this page.
Once you have gone to the Custom fields page (see Configuring the Checklist custom field), click Edit Parameters to customize the various checklist settings:
The following page will appear:
These parameters control the functionalities of the checklist.
The following effects occur:
Mandatory checklist items do not actually require users to check them. However, this effect can be achieved with a validator (see Setting up a Checklist Workflow Validator).
The existence of this feature is ignored completely, and new checklist items are not considered to be either mandatory or optional, and will appear as a standard checkbox without an asterisk. If this feature is enabled at a later date, any checklist items that were created while the feature was off will be considered mandatory by default.
Default Mandatory State
Created items will be mandatory by default.
Created items will be optional by default.
Users can assign statuses to checklist items. The default statuses are N/A, In Progress, and Blocked; you can also create custom statuses.
Users cannot assign statuses to checklist items.
Lock on Resolution
Global items that are added or updated will not be reflected in Jira issues that have already been resolved.
WHY DO MY CLOSED ISSUES NO LONGER SHOW GLOBAL ITEMS?
In some cases, turning this parameter on may cause currently closed issues or issues closed without touching the checklist to not show global items anymore. By default, checklist data will only persist when the default values are added, modified, or deleted. To prevent this, users must modify and save checklists before closing the issue.
You can achieve this automatically with a post function (see Setting up a Modify Checklists post function) that appends no items to the checklist on transitions resolving/closing the issue. This will force the checklist to persist its data to the database and produce the expected behavior.
Global items that are added, updated or removed will be reflected in all Jira issues, even if they have already been resolved. Reindexing is required to see those changes in searches.
Convert to Issue
Users can convert checklist items to Jira issues.
You can also select an issue link type, which will be used to automatically create an issue link between the created issue and the original issue. In the Convert items to issues dialog, the selected issue link type will be pre-selected.
Users cannot convert checklist items to Jira issues.
Users can bulk edit checklist items in issues.
Users cannot bulk edit checklist items in issues.
Users can bulk complete checklist items in issues.
Users cannot bulk complete checklist items in issues.
Users can assign due dates to checklist items.
Users cannot assign due dates to checklist items.
Users can assign priorities to checklist items. The priorities that are available come from the priority scheme currently in use for the project.
Users cannot assign priorities to checklist items.
Users can assign checklist items to themselves or other users.
Users cannot assign checklist items to anyone.
Users can format their checklists using the full Markdown suite (CommonMark specification), with the exception of HTML blocks.
Users can only format their checklists using basic Markdown (italics, bold, and hyperlinks).
Users can embed external images using Markdown syntax.
Users cannot embed external images.
Users can create headers to group together checklist items.
Users cannot create headers.
If this feature was enabled and then is later disabled, existing headers are not converted to regular items; instead, it simply removes the ability to create new headers and convert items to headers.
Look & Feel
These parameters control the visual appearance of the checklist.
These parameters apply to the checklist in general.
When the checklist is in read-only view, a strike through effect will be applied to checklist items when they are checked.
This is disabled in edit views, such as the panel display modes and Agile boards.
No strikethrough effect will be applied to checklist items when they are checked.
Show More Count
On the issue details page, only a certain number of checklist items will be listed before a show more link is displayed. The checklist must be in read-only view for this feature to work, which means that Display Mode must be set to Custom field.
All checklist items are always displayed.
Show Checklist With No Items
If Display Mode is set to Custom field, the checklist will still appear in the issue detail view if it contains no items.
The checklist will not appear in the issue detail view if it contains no items.
Show Checklist With Items Unchecked
If Display Mode is set to Custom field, the checklist will still appear in the issue detail view if none of its items are checked.
The checklist will not appear in the issue detail view if none of its items are checked.
Applies the selected display mode to the checklist in the issue details view:
With the Independent panel and Sidebar panel display modes, the operations bar in the issue views will not update when a workflow condition is in effect.
For more information, see Panel display modes limitation.
Indicates how the assignee is displayed on a checklist item.
Indicates how the description is displayed on a checklist item.
The checklist’s view will be more compact, saving vertical scrolling for longer checklists.
This feature flag is does not affect certain views, such as the Confluence and HTML exports or default checklist renders in the Search Issue page.
The checklist will have the default look and feel.
Show Only Checked Items
The checklist behaves like a standard Checkboxes custom field, where only checked items are displayed in the preview.
Since the Independent panel and Sidebar panel display modes do not have a read-only view, this feature only applies to the Custom Field display mode.
All items are rendered in the read-only view.
The checklist will limit it’s maximum width to 1024 pixels.
The checklist will expand its width without limit. Useful if you want to make use of all the available space.
These parameters apply to the checklist’s header specifically.
A header is displayed at the very top of the checklist that shows completion progress and checklist operations.
No header is displayed at the very top of the checklist.
Choose how the header’s banner and progress bar should calculate progression:
Changing this parameter changes how the checklist progression is calculated. It also changes how the checklist determines what Custom Banner Labels to display.
Choose a color scheme for the banner:
The type of banner that will be displayed:
Custom Banner Labels
This section is only enabled when Custom Labels is selected for Banner Type in the section above. It allows you to specify custom banners to display when the checklist reaches different levels of completion.
Displays the entered custom status when the entire checklist is complete.
Displays the entered custom status when the checklist is partially complete.
Displays the entered custom status when all mandatory items in the checklist are complete.
Displays the entered custom status when the checklist contains no items.
These parameters control complex features of the checklist.
The default XML renderer is replaced by a Confluence renderer, which allows checklists to display properly in Confluence.
When this feature is enabled, XML exports will no longer work properly.
The default XML renderer is used, which is better suited to exporting in XML. If you need to export in XML and need to disable this parameter, set up a Checklist Read-Only Proxy custom field instead to display your checklist in Confluence.