# Inside the Build: How Asana makes complex rules work everywhere

> Take a look inside the build to see how Asana's new rule and branch duplication and branch reordering features give teams a faster way to reuse the automations that already work.

Source: https://asana.com/ko/resources/how-asana-makes-complex-rules-work-everywhere

## Inside the Build: How Asana makes complex rules work everywhere

A growth marketing team builds an intake [rule in Asana](https://asana.com/features/workflow-automation/rules) that handles their repetitive tasks. The rule handles every incoming request: One branch for high priority requests spins up and assigns subtasks so that the team can get straight to work. Another for medium-priority tasks uses AI to summarize the request and suggest next steps. A third routes low-priority requests to the team's backlog with a due date. The rule is complex, and it works beautifully.

Then the sales team wants to use it too. And customer success.

Until recently, every team would have had to rebuild this rule by hand.

That's the challenge that kicked off Asana's update to the rule builder. With rule duplication, branch duplication, and branch reordering, the automations that already work for one team now work for everyone.

### The customer requests behind rule and branch duplication

The friction was sharpest for power users: the teams building sophisticated, multi-branch logic across multiple projects and portfolios. But the feedback didn't come from a single conversation. It built up over months across community forum posts, customer calls, and feature requests. 

“I kept hearing how painful it was to recreate some of these really complex rules that people were trying to build," says Julio Buendia, the product manager at Asana who leads this work. “It was tough to manage all these complex rules, and folks were interested in the ability to easily copy rules from one project to another.”

## Inside Asana's new rule duplication and branch management features

There could have been a simpler version of this launch: just reorder branches, and maybe allow duplication within a single project. That would have been a useful improvement, but it wouldn't have solved the real problem.

"We wanted to answer our customer's biggest pains, which was around the duplication of complex branch logic as well as the duplication of complex rules to other projects," Julio says.

The update introduces four closely related capabilities inside the rule builder:
- **Rule duplication within the same project:** Click the three-dot menu on any rule and hit duplicate.
- **Rule duplication across projects:**Copy a rule from one project into any other project where it would be useful.
- **Branch duplication inside a rule:** Reuse the logic of an existing branch without rewriting it—especially handy when a branch contains detailed task creation steps or AI instructions.
- **Branch reordering:** Move branches up or down to organize complex rules in a way that makes sense to the team maintaining them.

### Making rule duplication work across mismatched projects

Two challenges shaped how the feature came together.

The first was a design challenge. Rule duplication had to be obvious without cluttering an already-dense builder. The Rules Experience team made targeted tweaks to how branches are added and duplicated, and worked to clearly communicate what gets carried over when a rule is copied into a new project. This includes things like custom fields and sections that the target project might not yet have.

The second was a technical one. A rule often depends on specific pieces of a project—a custom field it checks, a section it moves tasks into. What happens when someone copies that rule into a project that doesn't have those pieces yet?

The Rules Experience team built the feature to handle those gaps, so duplication works across projects that aren't perfect mirrors of each other.

Rules are less scary now. If you create a complex branch, you don't have to worry about having to rewrite that logic by hand.

## Asana's customer-first product development

The story of this launch is the story of how Asana builds: listen closely, share what's coming, and adjust based on what customers tell us.

“Our customers are our biggest sources of inspiration,” Julio says. “The feedback they share—whether in product, on forums, on social media—those are some of the things that we as PMs at Asana really watch and listen to and make sure we actually incorporate into Asana to make our customers' lives a lot better.”

This feature came from the forum. The next one could too. Try rule duplication and tell us what to build next.

#### Supercharge your teams with AI that gets work done

Give your teams AI that understands their work, keeps projects moving, and gets better the more your teams use it.
- [영업팀에 문의](http://asana.com/ai-teammates-sales?utm_medium=website&amp;utm_source=blog&amp;utm_campaign=aitga-sl27)
- [영업팀에 문의](http://asana.com/ai-teammates-sales?utm_medium=website&amp;utm_source=blog&amp;utm_campaign=aitga-sl27)

워크플로 자동화

- [업무 환경에서의 AI: 지금 바로 AI를 활용하는 방법](https://resources.asana.com/ai-at-work?utm_medium=web&utm_source=resource-card&utm_campaign=ai25)

업무 환경에서의 AI

- [Planning to execution: Connecting goals to work in 2024](https://resources.asana.com/connecting-goals-to-work)

전략적 계획 수립

- [릴리스 관리: 성공적인 프로세스를 위한 5가지 단계](/ko/resources/release-management)

애자일

#### 콘텐츠 작가

소프트웨어 릴리스를 경험해 본 적이 있다면 이 일이 얼마나 복잡해질 수 있는지 잘 아실 것입니다. 프로젝트 타임라인을 관리하는 일부터 마감일과 범위를 추적하는 일까지, 한 사람이 감당하기에는 너무 많은 일이 주어집니다. 이럴 때 릴리스 관리 프로세스가 효과를 발휘합니다. 적절한 프로세스가 갖춰져 있으면 가장 복잡한 작업 ...

- [명확하고 반복 가능한 워크플로를 생성할 수 있는 간단한 7단계](/ko/resources/workflow-examples)

프로젝트 관리

비즈니스 전략

#### 글쓴이

워크플로라는 단어는 모호합니다. 프로세스를 의미할 때도 있고, 정보를 정리하는 방식을 의미하기도 합니다.용어의 모호성은 실제로 큰 영향을 미칩니다. 워크플로가 무엇인지 명확하지 않으면 업무 자체에 혼란을 초래하여 효율성이 떨어질 수 있기 때문입니다. 예를 들어, 평균적인 지식 근로자는 근무 시간의 60%를 정보를 검색하 ...

- [Inside the Build: How Asana makes complex rules work everywhere](/ko/resources/how-asana-makes-complex-rules-work-everywhere)

워크플로 자동화

워크플로 자동화

- [Content marketing manager](/author/lauren-johnson)

A growth marketing team builds an intake rule in Asana that handles their repetitive tasks. The rule handles every incoming request: One branch for high priority requests spins up ...
