For anyone who has created a schedule, one of the essential things to know is percent complete. Users of OnePager know we already offer ways to show percent complete via a yellow bar, text, or a checkmark. However, we will dive into another method: color coding different tasks based on a percent complete range.
We will first want to determine what percent complete ranges we want to create rules for and what color will represent them. In this example, I will be using the following ranges.
Welcome to part 3 of the task link filtering trilogy! Through our task link journey, we have covered how to display dependencies that are on a Critical Path (Part 1) and also dependencies that are set for Future Dates (Part 2). If you missed either of those two blog posts, I highly suggest you treat yourself to the wealth of knowledge it offers regarding task link filtering.
We will discuss how to filter your task links so that only ones with a milestone as a successor are displayed. To do this, we will first need to create a chart with task links enabled. You can enable the task links by going into Chart Properties > Task Links and checking the box “Show data-driven links.”
Welcome to part 2 of the task link filtering trilogy! Our last blog article discussed how to show task links on a Critical Path (Part 1). This portion will explore how you can filter your task links in two more ways, both relating to future dates. The first will go over how to filter task links with a status of “Future Tasks,” while the second will be how to filter task links to only show when they are to the right of your Time Cursor, which is another way of looking at future dependencies.
We will be doing a three-part blog series that explores smart ways to filter your task links in a OnePager chart. This first article will discuss how to display dependencies for only the tasks that are on the critical path. We will use the Microsoft Project example below, where Site 1 and all of its subtasks are on the critical path, and all of the tasks underneath Site 2 are non-critical:
If you are a regular user of OnePager Pro with Microsoft Project, you already know about Flag20 and how it’s used to bring over tasks with a Yes value. However, there might be instances where you want to filter your tasks further and exclude tasks once they have finished. When this situation arises, you can use Conditional Import Rules to check not only for Flag20, but also for an incomplete status.
Let’s say we need OnePager to know when a task or milestone finishes so that it can be removed from the chart. Right out of the gate, this sounds like a very tedious task as you would need to not only track the status of each task but also mark them as No in your Flag20 field once they finish. Fear not, though, as there is a much faster and easier way to do this.
When creating a schedule, one thing stands out when presenting to an audience: the percent complete. While it is nice to see the start and finish date for the summary tasks in the schedule, it is essential to show how far along a task is. Most of the time, your project plan’s percent complete values will suffice, but there are other times where the percent complete might seem ahead or behind schedule. In this blog, we will discuss what OnePager has to offer to remedy this issue: a feature called %Complete EV.
Before we begin discussing this exciting feature in OnePager, I want to clarify that this is a OnePager proprietary calculation that only looks at the percent complete for summary tasks. If you find that your issues are with the non-summary tasks, you should check out our blog that covers that issue here.
Microsoft Project averages all the tasks under the summary task, giving you an overall percent complete. However, this calculation can be incorrect due to other factors that Microsoft Project didn’t consider, which is what OnePager %Complete EV fixes. If you look at the example below, you will see that the Summary Task is behind schedule, even though all of its children are right on track.
In my view, among the many great features of OnePager, none beat Conditional Formatting. With Conditional Formatting, you can create rules to change the color, shape, fill, and other properties of tasks and milestones based on specific rules that you set. However, what happens when you have multiple values to which you need the same rule to apply? You could create a bunch of separate rules, but that’s a lot of work. In this article, we will go over how you can create a conditional formatting rule that tests for multiple conditions at once.
Imagine with me, if you will, that you have a schedule with individual resources assigned to different tasks. Each resource is part of a specific team in your organization, and you would like to be able to color tasks based on the team that the people belong to, not based on their individual names.