A feature is a means to an end. It’s never about the feature, but what it enables you to do.
There are a lot of reasons why you’d want to be able to Increment a custom number field with a rule action
The simplest to implement would be Tracking the number of times a task changes between section
The reason for wanting this would be to have it serve as an indicator of process (in)efficiency. If tasks in a process regularly switch sections more often than there are steps in the process this is probably worth investigating.
This is how to set it up:
- Create a custom number field section movements
- Create a rule with AI studio like so:
- Although GPT-4o is probably be the most accurate model for numerical operations this seems overkill, so I’ve selected GPT-4o mini
- Set the instructions to
section movements = section movements +1
to be as clear and unambiguous as possible - Restrict the data and permissions as pulling information from other work/projects is unnecessary and would therefore be wasteful.
- Set the rule name to
📝 Log section movement
. I often use an emoji to easily spot which rule was running or has run:
A few caveats
- We can never be as sure of the accuracy of this rule as when Asana would implement incrementing a number.
- As computing power is concerned I can hardly think of a more expensive/inefficient way to increment a number. This is why I’d advise to use this sparingly, and only as long the process you’re evaluating has focus under an improvement initiative.
Jan-Rienk @ Improving Every Day