Version 6.1.0 was released on June 1, 2022.
Users can now browse templates from issues, which will give them access to more features regarding templates.
Users can now be marked as template owners, allowing them to edit templates through the template list opened from issues. By default, the creator of a template will become its owner.
Administrators are allowed to change the owner of a template.
After upgrading to 6.1, existing templates will have no owner.
Users can now favorite templates, making them available in the “Quick import” section of the template dropdown.
Administrators and project administrators can now pin importable templates, making them available for all users in the Quick import section of the template dropdown.
Issue conversion improvements
You can select an issue link type which will be used to automatically create an issue link between the issue created from the conversion and the original issue.
In the Convert items to issues dialog the selected issue link type will be pre-selected.
Issue keys in converted items
Converting items used to rename the items with the freshly created issue’s key. This approach didn’t work well with global items since these items cannot be renamed. The resulting issue key is now stored separately and can be seen at a glance in the items.
You can now assign users anywhere the Assign Users feature is enabled:
Default local items
Modify Checklists post functions
User assignment will follow user permissions once set in issues.
It is now possible to access the Bulk Editor in each of the section headings' menu, which will only update items in that specific heading.
A more compact view is available to help scrolling in longer checklists.
The default mandatory state of items can now be configured.
We’ve added and documented new REST APIs to use.
POST Create templates
PUT Update templates
GET Get templates
DELETE Delete templates
POST Favorite templates
DELETE Unfavorite templates
GET Get parameters
PUT Update parameters
GET Get examples
GET Get parameters
Select to have the checklist behave like a standard Checkboxes custom field where only checked items are displayed in the preview.
Before this release, the
allMandatoryItemsChecked() function returned issues where the checklist either had all of its mandatory items checked or contained no mandatory items at all. With this change, the function requires the checklist to contain at least one mandatory item.
This rule applies to both the positive and the negative filters.
Checklist = allMandatoryItemsChecked() and
Checklist != allMandatoryItemsChecked()
The following table shows the difference of results if you were to use the
Checklist = allMandatoryItemsChecked() function.
CHK-1253 The “Convert to subtask” menu action is hidden if you cannot create a subtask in the current issue.
CHK-1263 Improved the interface of the checklist configuration pages across the App.