Tech Tip: Onshape Tasks and Release Management

Onshape has powerful task assignment capabilities built right into your collaborative commenting features. This is a great way to track changes and ensure they are correctly made.

For today’s Tech Tip, let’s review a quick task assignment workflow, and how that interacts with Onshape release management

Creating and Assigning a Task

Tasks can be created two different ways:

1. Directly from the action items page, using the Create Task button in the top right corner. You can add references to a specific element of a document, as well as prioritization and a due date.

2. From a comment in a document. Here, you can tag the specific element on which you wish to focus the task.

These tasks not only clearly communicate what changes need to be made in a formal and tracked manner, but they can also play a role in release management, which we’ll look at next.

Open Tasks and Release Management

In this example, our company administrator has enabled a setting, found in the Company Settings > Release Management node that prevents a release candidate from being created if there are any unresolved tasks.

Notice that if a user attempts to create a new release of the handle, the release candidate cannot be created. This is because the pending task created in the comment is blocking its creation.

This particular administrative setting is a great way to drive responsibility and accountability for changes. Only once a user marks the task as complete can the new release candidate be generated.

After a recent Onshape release, tasks can now be assigned to more than one user simultaneously. Any of the assigned users may mark the task as resolved, allowing for further flexibility to break up tasks among design teams.

We hope you find that Onshape Tasks, coupled with release management controls, help drive clear and effective workflows in your design and change processes.