.png)
NEW Smart Issue Templates for Jira Cloud
Release Date:
Platform: Cloud
Version: 28.0.0
Release notes:
NEW A new look for Templates, Scopes and Hierarchies
The three screens you use most have been rebuilt to look and work like Jira itself: modern, simpler to read, and fewer clicks for the same job. Every feature you use today is still there, and there is nothing to reconfigure and nothing to migrate. See The new UI for what changes and what stays the same.
-
Tables you can shape: sort by any column, choose which columns you see, and find row actions in a menu on hover rather than competing for space in the row.
-
Every filter in a single popup, and each one now takes more than one value at a time.
-
Create and edit forms that match Jira's own create-issue dialog, down to the field layout, the work type icons and the pickers. If you can raise an issue in Jira, you already know these forms.
-
A hierarchy editor that is a real tree, in the style of Jira Plans: drag a node to move it, and edit its fields in a panel beside the tree without losing your place.
NEW Team field support
Jira's Team field can now be set on a template and on a hierarchy node, and it is carried through to the work items they create, so work arrives already assigned to the right team. The upgrade asks a Jira admin to approve two new permissions, so the app can read teams and their members.
NEW Import, export and delete in bulk
Housekeeping that used to be one item at a time now happens in a single action, for templates, scopes and hierarchies alike.
-
Select many and delete them together, with a preview of exactly what will go.
-
Export a list to a file and import it back, into the same site or a different one.
-
Protect an export with a password.
IMPROVED Migration from Jira Data Center with the Cloud Migration Assistant
Faster, more reliable, and far clearer when something does not fit.
-
Hierarchies now migrate with the Cloud Migration Assistant.
-
Anything that could not be brought across is named with the Data Center project, work type, component or version it came from, instead of a generic failure.
-
That report travels with exports and previews, so you can hand it to whoever needs to act on it.
-
Each problem is reported once, not once per record or per retry.
-
A check confirms every migrated record reached the listings, and the safety check compares real counts.
FIXED Fixes found while testing the new screens: a feature node is no longer dropped from a hierarchy when you navigate away from the editor, the Reporter list no longer shows "No matches" while users are still loading, and a hierarchy brought across by a migration can be saved again.