As an admin, workflows for status transitions are one of the most powerful tools in OpenProject. But with that power naturally comes complexity. That’s why we’ve improved the user experience for custom workflows in recent releases.

To help you get started, we’ve also updated our blog article on using workflows in OpenProject.

In our example, Luke is a developer working on features. He can move work packages from "In development" to "Needs testing", but not beyond that. Testing is handled by a dedicated QA team, so only QA team members should be able perform the next transition.

This is where workflows come in: they define who can set which status, depending on role and work package type.

Read the article to learn how to use custom workflows to model real-life responsibilities in your projects.