Create a custom workflow for recurring tasks¶

Planio is not only great for one-off projects. It really shines when it comes to recurring tasks that follow a certain workflow within your organization.

Follow along this guide to create a simple vacation approval workflow for your team members - and apply what you've learned to implement your own custom workflows.

Planio workflow basics¶

• Table of contents
• Create a custom workflow for recurring tasks
  • Planio workflow basics
    • Trackers
    • Issue statuses
    • Roles
    • Workflows
    • b

In Planio, every issue must belong to a tracker which defines its workflow. Let's look at this in more detail:

Trackers¶

We'd like to see trackers as special issue types. An issue must belong to exactly one tracker. Task, Support incident, Software bug, or -- you guessed it -- Vacation request would be great examples for a tracker.

Issue statuses¶

Issue statuses describe the different states, that an issue in Planio can have at any given moment. For instance, an issue can be Open, In progress, Waiting for review, or Closed. An issue will always have exactly one status and the status will likely change over time as people work on the issue.

Roles¶

Users in Planio have their own user account using which they take part in projects using one or more roles: While some users may take part as Manager, others may be Assistant or e.g. Client. The role defines what a user can and cannot see or do in a given project. It also defines the user's workflow.

Workflows¶

The workflow brings it all together: A workflow defines for every possible combination of tracker and role which issue statuses are available. It defines for all its tracker's issues which status changes are allowed and which issue properties are visible and/or changeable.

Say what!? This is arguably the most complex (and powerful) part of Planio, but don't worry -- we will walk you through it and you will be a workflow expert in no time!

Sample workflow for Managers working on Tasks.

b¶