Update Project Rule Trigger to differentiate between a Project "Status Change" vs. "Status Update"

English Forum Product Feedback
, ,
1

Currently there is a Rule Trigger at the Project-level for Status is changed.

project-status-changed
project-status-changed1002×1602 65.9 KB

However, I was surprised to find out that this rule fires whenever a new Status Update is posted, regardless of whether the status has actually changed since the previous update.

If you imagine this behavior through the lens of a conversation, it’s essentially…
Me - Hey Asana, let me know when the status on any of these projects changes.
Asana - This one just changed!
Me - Hey, good looking out! What did the status change to/from?
Asana - It went from ‘At risk’ to ‘At risk’
Me - That’s not a change, in fact that’s an update specifically saying the status hasn’t changed
Asana - :person_shrugging:

The key issue here is distinguishing between a Status Change and a Status Update.

Let’s say I have a project that was previously On track, but something came up and back on Jan 1st I had to change it to At risk. It’s now 3 weeks later and yesterday I posted a Status Update letting everyone know that the issues are still persisting and we’re trying new workarounds but the project remains At risk.

In this scenario, the status was Updated yesterday, but the status hasn’t Changed for 3 weeks.

1 Like
2

Any thoughts from our Top Forum Contributors on drawing this distinction between a Status Change vs. a Status Update?

cc: @lpb, @Richard_Sather, @Stephen_Li, @Bastien_Siebman, @Phil_Seeman

1 Like
3

I agree, @cosmo, and added my vote, and encourage others to as well.

I’d leave it up to the Asana product team how to implement and nomenclature to use, but I’d want to see another approach than using “change” and “update” to make the distinction because I generally consider those words as synonyms. It could be done with one “When” and one “If” for either/both conditions, or multiple "When"s.

Thanks,

Larry

2 Likes