Global items were previously configured in three different sections of the configuration page: Options, Default Value and Discretionary Options. These are now grouped into a single section called Global Items.
In V5, the way that global items (previously known as options) are stored in the database has changed. Upgrading to V5 will automatically migrate all options to the new, more flexible structure.
To make it possible to revert to a previous version, the previous options will be kept in the database. If you roll back to a previous version, the Checklist app will once again use the options that you had before you upgraded.
Support for HTML markup
The following new features have been introduced in V5.
The Emphasize Mandatory parameter has been replaced with the Mandatory Items setting. Whereas Emphasize Mandatory only showed an asterisk * next to a mandatory item, the Mandatory Items setting toggles the mandatory feature on and off completely.
The Section Headings feature is turned on by default. If you do not want this feature, you will need to turn it off after upgrading to V5 (seeEditing parameters).
Previously, you had to create the missing options exactly as they were in the backup before importing a project. With the new global items structure, missing global items are created automatically to match the backed-up project.
To determine whether a global item is missing, the name (complete Markdown text and description) and rank of the item are compared between the backup and instance.
For each missing global item, a warning will appear in the Import Validation step of the project import, informing the user that they will be created.
MISSING GLOBAL ITEM - No global item was found for custom field 'CF_NAME' in context 'CF_NAME Default Context' with name 'Item Name' at rank '1'. A new global item will be created from the backup.
The rank starts at 1, which indicates the order in which the global items appear.
Be careful of false positives caused by item ordering. If a global item is missing, the ranks of all the subsequent global items will shift ahead by one. Because their ranks will no longer be the same in both the backup and instance, the system will no longer see them as matches.
For example: In the backup, A=1, B=2, and C=3. In the instance, item A is missing, so B=1 and C=2. As a result, B and C are no longer considered to be matches.
With the changes to global items, the REST API structure has also changed. Any scripts that manipulate checklists using the REST API will have to be updated.
If you have scripts that modify Jira’s options table for a checklist field, they will no longer work. If you ever need to modify global items through scripting, please contact us.
Re-upgrading after a rollback
Global items are only migrated once. If you upgrade to V5, roll back, and then want to upgrade to V5 again, the global items will not be migrated again. This means that any changes that were made to global items after the rollback will not be migrated when you re-upgrade.
If this situation applies to you, please contact us before you upgrade to V5 again. A technical workaround exists, and we would be happy to help you through it.