Global Rules would rule! Create a library for Rules

Thanks for the input!

1 Like

Just to clarify my post here as it seems there was some confusion: as I mentioned, this Flowsana duplication capability applies to duplicating rules created in Flowsana, not to any Asana-created rules.

I would love to be able to provide an ability to duplicate Asana rules but it’s not currently technically possible because Asana does not expose those in its programming interface for external applications.

One of my main problems is doing sweeping changes to multiple projects at once, with identical rule set-ups. These projects each have the max of 20 rules. I’m assuming flowsana will not duplicate rules to projects which are already full? In which case, I’ll have to go in and delete the rules of the recipient projects in order for it to work?

Hi Trevor,

As mentioned above, the duplication feature in Flowsana pertains to Flowsana rules, not Asana rules. Flowsana rules are independent and unrelated to the 20-rule limit in Asana; also, Flowsana does not have the limit of 20 rules per project that Asana does.

As tasks can be added to multiple projects and you can add custom fields to carry that task progress into those multiple project, it would be GREAT to be able to copy a Rule and add to other projects.

Use Case
If I have a task in multiple projects and use a custom field for Not Started, In Progress, Completed, I have to create rules in EACH project to change that custom field as a task moves through a kanban.

Yup! This would be a really great feature!

Thanks for your feedback @Getz_Pro! We already have a thread requesting this feature so I’ve gone ahead and merged your post with the main request to consolidate feedback!

1 Like

It would be great if Asana added a “Copy Rule” function for rules that are set up for a specific project. When creating projects, I sometimes have to create multiple custom rules that have only slight differences to the actions or triggers that are configured for them. It would be great if I could copy from an existing rule instead of always having to create the custom rules from scratch.

Hi @Colin_Palamar, thanks for taking the time to provide this feedback :slight_smile:

This is a popular request and we do actually have an existing thread for this topic in the Forum! I’ve gone ahead and merged your post with this existing one to consolidate feedback.

I’ll keep you posted in the main thread on any updates! :slight_smile:

1 Like

Is this on the roadmap for Asana?

2 Likes

I work for a small company but we have well over 200 boards. If I want to add a simple rule like mark complete when a status is changed to xxx, I have to add a rule to every single board impacted. It would be an incredible time saver to be able to go to “Global Rules” and indicate which boards to include (or exclude if there was a select all option).

Is there a status update on this? As my organization becomes dependent on Asana for more of our workflows, this is critical. If we have hundreds of projects, applying the rules manually becomes unfeasible. Thanks.

+1 for this. Definitely need this.

Want to +1 on the library, and also stress the critical need to increase the limit of 20 rules per project, preferably to unlimited or at least 100-200. We are running into major issues due to this limitation and are even considering moving our projects to another tool. We now have to constantly make manual adjustments that the rules would be able to take over if only they were not limited to 20 (which barely allows to set up the most basic of rules). Another related suggestion would include adding if/then & and functionality to rules, e.g. field “name”–>set assignee could then be put as if “name=X”, assign “X” and if “name=Y”, assign “Y” etc.

Asana team: if you implement a rule library, I’ll be forever grateful.
In my case, we have a library of projects (40+) for which we need to enter manually the same 5 rules, over and over again. Choosing from a library would save a lot of time.

1 Like

If this is the place to vote for this functionality to be rolled out - here’s mine! :ballot_box:

This would be amazing. I’d also love to have a simple way to to make a rule be applied across all projects in the division (maybe restricted by the admin role only though) rather than having to apply to every new project

1 Like

A global library of rules would be so effective to replicate rules overall different projects!
We use templates which are copying the existing rules, but if any changes we need to look for each rule and update it one by one. Really difficult to maintain it.
Also applying a new rule on 10+ templates is an extensive process.

It would add a lot of value to Asana for sure!

Yes this would be great. I have seen some commentary about the ‘rule ownership’ structure being a problem when removing users. For my tasks, it is all good to have the user own the rule, but for everything else, this seems problematic and does not really seem logical. If we create a rule in a project, for a project, I think it stands to reason that ownership of that rule should be tied to the project, not the person who created it so the rule does not get paused if they leave the company, or the project.

There is another item I have noticed that I would love to see changed which is how dates are defined in some rules. Example would be for something like moving a task to a section for tasks with no due date. Currently. I can define the trigger as being ‘due date removed’ but this is not universally true as I may have a task where I never set one to begin with, but I want my task to go to that section. Thus, I would love this to be something like ‘Due date is unknown’. By the same token, we should be able to define dates more formulaicly. Due date = ‘today’ ; Due date is after ‘today’, due date is greater than ‘tomorrow’ etc… Just like we can do in other systems when defining searches to generate a list of items in a dynamicly updated list.