Do you see a status called Open? Great, you can skip this step.Navigate to Your avatar → Administration → Issue statuses.The steps are similar but slightly different for the three statuses Open, Approved, and Rejected. Do not select anything in the Copy workflow from drop down.We'll actually use those for the start and end of our vacations. Uncheck all Standard fields checkboxes except the ones for Start date and Due date.Uncheck the Issues displayed in roadmap checkbox since we do not want to see vacation days on our project roadmaps.Navigate to Your avatar → Administration → Trackers, then click on New tracker.To implement this, we will create a Tracker called Vacation request, three Issue statuses called Open, Approved, and Rejected, and two Roles, called Manager and Staff.įinally, we will tie all those together using a custom Workflow in Planio.
#WORKFLOWY CALENDAR HOW TO#
We will also show you how to visualise them on Planio's calendar, so you can get a great overview on who is on vacation at which point in time. We will now build this workflow in Planio allowing for actual vacation requests being made and approved. If disapproved, employees can alter their requested dates and re-request approval until - hopefully - they will be allowed their well-deserved days in the Caribbean. Upon approval, the dates of that vacation can not be altered, and the vacation request is final. Employees must submit a request mentioning the start and end date of the requested vacation and managers will approve or disapprove the request. In many companies, taking a vacation requires approval by a manager. Dreaming of that deserted beach in the Caribbean? Let's request some vacation days and off we go. 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! 2. It defines for all its tracker's issues which status changes are allowed and which issue properties are visible and/or changeable. The workflow brings it all together: A workflow defines for every possible combination of tracker and role which issue statuses are available. The role defines what a user can and cannot see or do in a given project. 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 regular Staff or e.g. An issue will always have exactly one status and the status will likely change over time as people work on the issue. For instance, an issue can be Open, In progress, Waiting for review, or Closed. Issue statuses describe the different states, that an issue in Planio can have at any given moment.
#WORKFLOWY CALENDAR SOFTWARE#
Task, Support incident, Software bug, or - you guessed it - Vacation request would be great examples for a tracker. An issue must belong to exactly one tracker.
We'd like to see trackers as special issue types. Let's look at this in more detail: Trackers In Planio, every issue must belong to a tracker which defines its workflow. Put it all to work in an actual project.
0 kommentar(er)
