The issue we are having is that the rule is set to check if the task has a Custom Field set to a specific value before executing the rule. In all the projects that have a copy of this rule functioning, there’s only ONE task in the whole project that has that custom field value set. However, the rule executes on ALL tasks, and it’s causing considerable “task history” junk update overflows on ALL the tasks and it’s really becoming problematic.
What are we doing wrong here? I’m posting a pic of the rule along with the details on the “Check If” condition and the ‘Do This’ action.
Again, this rule is running on every task in the project when due date is changed, NOT simply the ones that have that value set.
It also seems like it’s running once daily, and then also running any time someone changes the due date, even though these tasks do not even have a value in that custom field.
We very much need this rule working, but we very much need it not to be doing this to all the tasks that lack that custom field value. What are we doing wrong?
If I’m understanding that you set up your overall system per the other thread you linked to, then I don’t think those log entries are related to the rule you mention here. Rather, I think they are the result of the formula you’ve defined for the “DueDate-Today” custom field. That formula changes the value of that custom field once per day, and that’s the change which is getting logged. Does that make sense?
Is there any way to set this formula so that it doesn’t run on every task in the project? Right now I am not aware of any way to avoid that since all tasks within a project get the same custom fields.
