This release is about sharing. You can now share a saved view with people and teams in your organization, so a filtered, configured way of looking at your program can be handed to someone else instead of described to them. Alongside it, sharing changes on objects with approvals turned on now route to the owner as approval requests. This means that owners keep control of who gets access to what they own.
Notable Enhancements
Share saved views with people and teams
A saved view can now be shared with other users and teams in your organization. Recipients get the view read only: they can adjust display and filter settings while they are looking at it, they cannot save over your version, and they can duplicate it if they want their own copy. Before the share completes, you see which items in the view each recipient can and cannot see, and you can grant them access to the items you own in the same step. Shared views appear in their own section of the sidebar, and recipients are notified when a view is shared with them or when access is removed.
Approval requests for sharing changes
On objects with approvals turned on, an editor who adds a collaborator, removes a collaborator, or changes a collaborator's role now creates an approval request instead of an immediate change. The request goes to the owner, shows up alongside other approvals, and is recorded in the object's history and updates feed so there is a record of who asked for what and how it was resolved. Requests can now also cover teams that are domestically owned but include foreign members, which previously could not be requested at all. Until a request is approved, the editor keeps the access they already had, and anything created but not yet approved is clearly shown as pending rather than looking ready to use.
Reference identifiers
Identifiers now behave correctly when an object changes hands: an item transferred to a different company is reminted with an identifier belonging to its new owner, and you are warned before an ownership change moves an object across an organization boundary.
Bug Fixes
Importing an Excel workbook with multiple sheets now tells you which sheet is missing required date columns instead of showing a generic error, and it no longer lets you continue past the date step without mapping them.
PDF imports no longer produce a stray unnamed task in the preview, and tables that were previously read incorrectly now come through with the right columns and nesting. A flat task list with status and notes columns is no longer mistaken for a nested hierarchy.
Importing a file with an unsupported extension now fails immediately with a clear unreadable file message instead of retrying.
Bulk driver import from a CSV now actually creates the drivers.
Fixed a regression in Jira sync when creating an item from Integrate into Jira.
Dragging the Gantt scrollbar horizontally no longer jumps the schedule by more than a century, and the expand loading state now stays active until the Gantt has finished expanding.
The All Drivers button in a scenario sidebar is now disabled, so it no longer takes you out of the scenario and into table view.
Long names now truncate or wrap instead of overflowing across the product: custom statuses on the settings page, team names in the add member dialog, object names in the add parent dialog and in notification summaries, and view names next to the sidebar menu button.
Long text in a text attribute field stays inside the viewport instead of running off screen.
The assignee column in table view no longer overlaps the more indicator with the add assignee field.
Object names in notification summaries render at the correct size.