November 24, 2022

November 10, 2022

November 03, 2022

November 24, 2022


Organize information better with our revamped Text editor

Say hello to our freshly overhauled editor. Working on descriptions and comments is finally fun (again).

The modern rich text editor allows you to communicate more effectively, organize information easily, and provide more clarity. It offers a wider array of editing possibilities such as slash commands, a floating formatting toolbar, drag-and-drop content blocks, and much more.

With more ways to present information within items and comments, airfocus enables your teams to have the proper context they need to build the right product faster.

Here are all the upgrades:

  • The Text editor is available for item descriptions and comments (even for item descriptions on Portal).

  • Slash commands: With / you can add various blocks to your item description and comments. You can also turn a block into another block type such as Text, h1, h2, h3, numbered list, bulleted lists, code block, and @mention.

  • Floating formatting toolbar: We offer advanced formatting with our new editing toolbar which is hidden but will appear exactly at the place of highlight or action.

  • Drag-and-drop rearrangement for content blocks: You can now easily drag-and-drop blocks within the item description or comments.

  • Keyboard shortcuts: Use commonly known shortcuts to speed up your work. Find all shortcuts here.

  • Improved hyperlinks: When you want to link a specific text, you can now easily paste links with ⌘ + V / Ctrl V.

Choose how to display item progress

You can now configure item progress in your workspace hierarchy settings to display in absolute numbers or percentages.

UX improvements

We’ve added more intuitive dependency and hierarchy linking. Furthermore, we've added status icons on dependency and hierarchy cards within your item panel.

Bug fixes 🐞

  • When duplicating workspaces, Item color and Item type from the original workspace are now copied over accurately to the new workspace.

November 10, 2022


New ‘Status’ field aligns your team on status definitions and brings clarity on item progress

airfocus workspaces now have a dedicated system field to assign status to your items.

The Status field has standardized status categories with customizable statuses per category to suit your team’s workflows. Get alignment and a clear view of what needs to be started, what’s in progress, and what’s completed – without the struggle of manually configuring a custom field on every workspace.

Status provides a holistic view of item progress across hierarchy levels and workspaces. You can track the progress of parent items (e.g. Jira epic) based on how many of its child items (e.g. Jira stories) have been closed.

In essence:

  • The mandatory Status field gets more visibility on all your views.

  • There are three fixed global Status categories - Draft, Active, Closed - with the option to create as many statuses per category as you need to organize your team’s workflows.

  • With airfocus Hierarchy enabled, you can track progress on parent items based on closed child items.

  • Each category follows its own business logic impacting your workflows. For example, closed items advance progress and draft items are not being shown on share links or portals.

  • You can use status categories as board columns or swimlanes to group and visualize what's in Draft, Active, or Closed. This is especially useful for different levels of granularity.

  • You can get notifications for status changes on assigned items or by “watching” them.

  • We offer an easy-to-use migration tool to move a custom select field to the new system status field.

  • In the future, airfocus functionality and apps will build upon Status field so we recommend switching now.

November 03, 2022


Disable users easily

To have better control over who can access your airfocus workspaces, you can now easily disable users when needed.

Bug fixes 🐞

  • Fixed a bug that causes the integration authorization with Azure DevOps not to work.

  • The dependencies on the timeline view are now displayed correctly.

Did this answer your question?