Josh has over a decade worth of experience in IT. Eight years of that was in healthcare doing IT Security (IAM) and Clinical Application Support. He now brings that experience to OnePager, where he provides support and brings new users up to speed with training sessions. Josh is an avid backpacker and enjoys spending nights deep in the woods outside of work.
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.
When creating a schedule in an Excel spreadsheet, you will have a Start date and Finish date. But there is also a time associated with those dates, and if you don’t set it, your tasks may appear to finish earlier than expected. In the example below, both tasks finish on the seventh day, but the blue task finishes at 12:00 a.m. and the red task finishes at 11:59 p.m., almost a full day later. Paying attention to the times associated with your dates in Excel will help you ensure that a task is scheduled correctly.
This blog will go over an addition to make to the formula in your Excel spreadsheet to change the time of your task Finish date.
OnePager’s baseline display is a great way to compare your original project plan to the way things are now. But what if you want to only show baselines where there has actually been a change in the underlying schedule? This blog article will show you how to conditionally display Baseline Markers when there is variance between Start/Finish and Baseline Start/Baseline Finish.
To display Baseline Markers conditionally, we first need to have our data set up correctly in our Microsoft Project file. We assume you already have a Task Name with Start/Finish dates. You will also need to have Baseline Start and Baseline Finish entries.
With a Gantt chart, you can display Start/Finish dates that show exactly when a task starts and finishes. However, in this blog, we will be creating a dateless chart to show a graphical representation of your schedule without any specific dates displayed.
We will start at the top of the chart with the Time Axis representing different tic units. In the example, we utilize the Month and Week units of the Time Axis.
In Microsoft Project, a field called Finish Variance shows how many days there are between the Finish and the Baseline Finish fields. Using this data can be helpful when trying to determine if your tasks are finishing on, before, or after their planned finish dates.
If you want to use the Finish Variance field in your OnePager Conditional Formatting Rules to show visually if your tasks are late, you’ll run into an issue: Microsoft Project treats Finish Variance as a string field instead of a number.
When creating a chart in OnePager, we want to make sure that the audience knows what the tasks and milestones represent. This is why the labels in a chart are so important.
Most of the time, using the same text field from MS Project will suffice for both your tasks and your milestones, but there are situations where you need to label tasks one way and milestones another. In this article, we are going to discuss how you can import data from two different Microsoft Project fields so that you can use the first field to label your tasks and the second field to label your milestones.