Hi All,
In one of the portfolio’s I want to have a customized colum that identifies (Yes / No) if the due date of the project is outdated. I know I can see the dates (start and due date is the same column) and they are displayed in red when the date is in the past. However, I would like to have tis visible in a different way.
Any suggestions?
@Niels_Oomen You can add a custom field to your portfolio: Due Date Past (or whatever you would like to name it). Set this as a single-select field. You can have Yes and No as options or just Yes. Then add a rule for when work is overdue, change Due Date Past to Yes.
Dear @Ron_Sanga,
Thanks for the feedback. I added a single-select field and I have created a run. But the single-select field is not changing. How can I trigger to run the rule (btw is the rule correct)? I have various projects where the due date is in the past with more then 1 day.
Thanks for the feedback.
@Niels_Oomen The rule will only run when a project changes to 1 day overdue. Meaning, any projects that are currently past due, the rule will not trigger. There are a couple ways to do this:
Just in case you aren’t familiar with it, there are a couple of ways you can view your overdue projects.
This will show only those projects in the portfolio that are overdue. You can then select all the projects by clicking on your first project, hold shift, then click on the last project. Then change your past due field to “Yes”.
hi @Ron_Sanga ,
Thanks again. I was familiar with the filtering, but I want to see all projects in the view an high-light the projects which needs an update (due date in the past). So, the single-select column should help.
However, I’m not familiair with: “Set the trigger to also be run manually”. I’m ok if this is a one-time actions per project (I know I can do it manually myself) but by using the trigger I also can validate the rule. Any advice on how I can do that?
I don’t think you need the manual rule trigger. Just sort by due date and flip the field directly for projects due in the past.
Overdue project dates (in the past and not marked complete) should turn up red btw. Assuming you use the native due date field.
Apperently I’m doing someting wrong. Below you see the rule, but nothing was set by the rule. I included when the due date was empty. So, I still due not know what is wrong.
@Niels_Oomen The trigger for your rule is When Work is overdue 1 day after. If Due date is empty the rule won’t run because there is no due date to trigger. Try setting a due date for today then see if the rule runs overnight. It should because once tomorrow comes, then the project is overdue by one day. You can do this on a test project if you would like so as to not affect any live projects.
Also, you really don’t need the check if in the rule as you have it above because in your trigger you are already checking for the due date to be 1 day overdue.
Just a reminder, the rule won’t run on projects that are already overdue because the trigger has passed.
This I did not knew this. I will check tomorrow again.
Nothing happend. Apperently I’m doing something wrong with this rule
For a project I did set the due date to 14-01-2026. But it is not set to out of date = Yes.
@Niels_Oomen One thing you might try is removing the Check if’s. They are not really needed with the way you structured your When trigger. The rule should then trigger and update the Out of date field.
@Niels_Oomen, I agree with @Ron_Sanga’s last reply that both Check ifs are not needed and you should remove them to simplify. But I suspect the problem is that the due date was 14-1 but just after midnight when the rule ran, today’s date was 16-1, so it’s expected that the action wouldn’t trigger because the task is 2 days overdue not 1 day overdue; it must match exactly as was pointed out earlier.
Thanks,
Larry
Hi All,
Last Friday the 16th I updated the rule as suggested (below). I updated various projects with an due date of the 15th and 16th and none of them have “Out of date” = Yes.
What should I do when some projects do not have a due date at all? Because then we do not have the date issue / challenge.
@Niels_Oomen The only thing I can think of with setting the project due date to 1/16 and it not switching is if the work schedule for the project is set to Monday - Friday. I haven’t tested this. @lpb do you know if the project work schedule would impact the rule running for one day past due?
@Niels_Oomen You can check the project schedule by going to the customize button in the project and clicking on Project Settings at the bottom. For projects without a due date, you can add the due date if you know what that is or add a task for the project owner to add the due date.
I don’t think the work schedule has to do with this, but I didn’t test.
@Niels_Oomen, yesterday the 18th I set a due date of the 18th for two work items in portfolio (one a project, one a portfolio) with this rule:
Both updated to High as expected just after midnight (the 19th).
Try these troubleshooting steps, then please create a support ticket: see How to contact our Support Team.
Thanks,
Larry
Thanks for the feedback. I updated a project in the portfolio with a due date to the 20th (today) and then I would expect that the configured field is updated tomorrow the 21st (after midnight).
It still did not work.
What should the rule be in case the column should also be triggered whne there is no due date at all?
