# 🚀 We replaced all our Status fields with Task types (a guide on migrating your existing workflows to use task types)

**URL:** <https://forum.asana.com/t/we-replaced-all-our-status-fields-with-task-types-a-guide-on-migrating-your-existing-workflows-to-use-task-types/1110357>\
**Category:** Forum Leader tips\
**Tags:** forum-leader-tip, custom-task-types\
**Created:** [21 November 2025 13:19 UTC](https://forum.asana.com/t/we-replaced-all-our-status-fields-with-task-types-a-guide-on-migrating-your-existing-workflows-to-use-task-types/1110357 "2025-11-21T13:19:18Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![Richard\_Sather](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/richard_sather/32/276096_2.png) [@Richard\_Sather](https://forum.asana.com/u/Richard_Sather)\
**Post date:** [21 November 2025 13:19 UTC](https://forum.asana.com/t/we-replaced-all-our-status-fields-with-task-types-a-guide-on-migrating-your-existing-workflows-to-use-task-types/1110357/1 "2025-11-21T13:19:19Z")

</div>

We’ve now migrated 95% of all active tasks (excluding subtasks) in our Asana space to use Custom Task Types - and we’re not going back - it’s a massive UX improvement.

Instead of showing task statuses in a dropdown that is buried in the Fields section of a task, each task shows its status directly where the checkmark used to be - more visible, more informative, more intuitive.

In case you want to do the same, I’ve put together the below guide of how you can enhance your existing workflows by migrating your **Sections** or **Single-select fields** (of statuses / stages / phases) to using Custom Task Types instead.

 ![image](https://us1.discourse-cdn.com/asana/original/4X/c/8/7/c879cb5f7556b715dd31e2cd73141c34ba83064e.jpeg)

Not sure what task types are, or what are their benefits? You may perhaps want to start [here](https://forum.asana.com/t/the-asana-feature-i-wish-i-d-discovered-sooner-custom-task-types/1110330).

⚠ Before you proceed, please make sure you review [this article, listing the caveats and current limitations of Custom task types.](https://forum.asana.com/t/custom-task-types-what-you-need-to-know-before-you-go-all-in/1108888)

# **1. Map your Single-select field (or Sections) to a Task Type**

**1.1.** Edit your single-select field to display all its options. If you use Asana in a browser, you could open another Asana tab and click on **Customize \> Task types and templates** and click on the **+Add task type** button and then **Create new** at the bottom of the dropdown list.

**1.2.** Type the name of your task type. Note, this should be written in the singular and describe what your task type actually _is_ . This is different to the name of your single-select field which may be called ‘Status’, for example so don’t just copy/paste it over to the task type.

As a clue for naming your new task type, look to the name of your ongoing process project. If your project is called ‘Requests’, your task type should be called ‘Request’. Here are some more examples of task type names: To-do, Lead, Client, Quote, Proposal, Contract, Invoice, Expense, Post, Campaign, Bug, Applicant, Vendor, Order, Property etc.

**1.3.** Recreate all the options in the task type. For ease of copy-pasting across, place both tabs side by side, like this:

 ![image](https://us1.discourse-cdn.com/asana/original/4X/1/5/7/15753aaa4f5a97806001caece275ff16836784fd.png)

You will notice that the statuses of a task type are divided into two clearly defined categories: **Active** and **Done**. The statuses in **Active** will keep the task incomplete, while the **Done** will complete the task, automatically, without any rules involved. So make sure to choose wisely! In the above example, we have decided that ‘PMO approved’ and the ‘Rejected’ statuses will both close/complete the task.

Note, that you do not need to copy/paste any emojis into the name of your task type’s statuses. Instead, paste them into the **Custom character** or right-click and select emoji if you are using a browser. (In the desktop app, use Win+Period, or if you are on a Mac use Ctrl+Cmd+Space)

 ![image](https://us1.discourse-cdn.com/asana/original/4X/7/e/6/7e604732726322ed95b1a451c1b212d762aa387f.jpeg)

If you are using **Sections** instead of a Single-select field for your statuses, use the same logic to map them over to a task type, like this:

 ![image](https://us1.discourse-cdn.com/asana/original/4X/5/9/b/59bb18b426b4cebde1252fc2d52589cdd5cf00ca.jpeg)

**❗ Do not remove your single-select field or delete your sections, yet!**

# **2. Convert all tasks to your new Task type**

**2.1.** In the list view, remove all filters in your project to reveal every task in the project. Optionally, but recommended, reveal the completed tasks too.

**2.2.** In the list view, select all the tasks in the project; incomplete and optionally, but recommended, the completed tasks too. For more control, click on the first task, just scroll down, hold shift and click on the last task. Once selected, use the bulk-action bar to convert task to your new task type, as per below:

 ![image](https://us1.discourse-cdn.com/asana/original/4X/5/0/2/502e6c0bfcb40befd04aa45e479e8ecf887e2876.jpeg)

This action is safe to carry out because there are no rules involved with your task type, yet.  
You will notice all the incomplete tasks will be marked as your first **Active** status, in my example, they are all at ‘🔍 Validation’ status, while all your completed tasks will be marked as the first **Done** status, which in my case is ‘✅ PMO approved’ status. This is not a problem, we are going to fix this with a temporary rule…

# **3. Create a temporary Rule to map all Task Type Statuses**

To efficiently map all your single-select field’s status values to the new task type, I recommend creating a temporary rule that we can then apply to all tasks. This rule also overcomes the current limitation that you cannot change the task type status of multiple tasks as a bulk action.

**3.1.** Click on **Customize** \> **Rules** \> **Add**.

**3.2.** In the rule Editor, for your **When** , select the first option on the right panel, **Rule is run manually** and label it as ‘Map statuses’ or anything you like.

**3.3.** In the **Check if** boxes, populate them with _all_ the statuses of your single-select status field by using the **Otherwise if…**

 ![image](https://us1.discourse-cdn.com/asana/original/4X/6/5/6/6560a5ac78afebec44ed9cce59df41ee2c68e001.jpeg)  
If you are using **Sections** instead of a single-select field for your statuses in your project, replace all the **Check if** boxes with the **Task is in section…** condition.

**3.4.** In the **Do this** boxes, scroll in the right panel and choose **Set [name of your task type] to..**. (_not_ Set task type to, which is listed in the actions, below) and choose the equivalent status as your **Check if** boxes. Do this to each of your **Do this** boxes:

 ![image](https://us1.discourse-cdn.com/asana/original/4X/c/6/c/c6cb6bb7266252f8220135e35012d5c1dfc247e1.jpeg)  
Your rule should end up look like this if you are using single-select field for your status:  
 ![image](https://us1.discourse-cdn.com/asana/original/4X/d/b/5/db53f190d528fcd4901c1d1f1958574e83157e52.png)

💡 For the first status, in my case, ‘🔍 Validation’ was already set automatically to all _incomplete_ tasks when they were converted to a task type in step 2.2 because it is my first **Active** status. So you could skip this action. The same applies to your first **Done** status which was also set to all _completed_ tasks in step 2.2.

**3.5.** Publish/save the rule once you have mapped all your statuses.

# **4. Run rule on all tasks to set the correct Task Type Statuses**

Ok so we are ready to map all our tasks to the correct task types status but before we get all excited, it’s always a good idea to test your rule on a few tasks before we proceed with applying in bulk!

**4.1.** In the list view, again, make sure to remove all filters in your project to reveal every task in the project. Optionally but recommended, reveal the completed tasks too. You may also want to keep your project **Group** ed by your Sections or the Single-select field of your status.

**4.2.** In the list view, right click on a task (which does _not_ have the correct task type status, such as in the second group or section) and select **Run a rule** and select the rule we labelled in step 3.2.

 ![image](https://us1.discourse-cdn.com/asana/original/4X/f/9/5/f95b766780cfd526631031dcb099332656647a40.jpeg)

Repeat on a few tasks with different statuses and verify that the rule has indeed corrected the task type’s status, matching your single-select field’s option or the Section that it is still currently in. If you are confident your rule is working correctly, move to the next step.

**4.3.** In the list view, multi-select 50 tasks at a time (this is due to a current limitation for triggering rules manually). For more control, click on the first task, just scroll down, hold shift and click on the 50th task. Once selected, use the bulk-action bar to run our rule manually, as per below:

 ![image](https://us1.discourse-cdn.com/asana/original/4X/a/6/2/a62635859bbac861c783d177ebc201ac6e677cec.jpeg)

**4.4.** Repeat step 4.3. in batches of 50, until all the tasks in the project are converted. Make sure that all tasks have the correct task type status.

Ok, we are almost there!

# **5. Setup your Project for the new Task type**

**5.1.** Review all your project’s view tabs and replace any **Filter** , **Sort** , **Group** settings that are using your Single-select status field (or Sections) to instead use your new task type.  
💡 You will find your task type at the bottom of the dropdowns of these settings with an ‘A’ icon in a square.  
⚠ Note certain caveats in section 2 & 6 of [this article](https://forum.asana.com/t/custom-task-types-what-you-need-to-know-before-you-go-all-in/1108888).

**5.2.** Review the **Dashboard** tab(s) and check for any charts that are using your Single-select status field (or Sections) and replace them with your new task type.  
⚠ Note certain caveats regarding Dashboards in section 6 of [this article](https://forum.asana.com/t/custom-task-types-what-you-need-to-know-before-you-go-all-in/1108888).

**5.3.** Review _all_ the rules in your project. Scan through to find all the rules that are using your single-select status field. If you are instead using Sections, you will note a ⚡ icon next to your Section name in the List or Board views; click on that icon to edit that rule.

Edit all these rules accordingly, by remapping their trigger, conditions and actions to use your task type, where applicable, by replacing the following:

- **When…** to '[Task type name] is changed…
- **Check if…** to '[Task type name] is…
- **Do this…** to 'Set '[Task type name] to…

⚠ Note certain caveats regarding Rules in section 5 of [this article](https://forum.asana.com/t/custom-task-types-what-you-need-to-know-before-you-go-all-in/1108888).

**5.4.** Make sure to review any rules that might be adding tasks to the project or into particular Sections. These rules are listed below the project’s rules in the Customize menu.

If you have rules from other projects that move tasks into particular Sections, you could leave your Sections in place so those rules don’t break. However, it is recommended to Group your project by your Task type’s statuses instead of Sections; so any Sections will not be ‘visible’ in such a view. You could remap the rules to set a particular task type status if they land in a particular Section, for example.

Remember that any task add into your project could be converted into a task type by using a simple rule such as ‘When task is added to the project, then convert to task type’. And there could be cases where another task type from another project could be converted to your task type when it enters your project/process. For example, when a ‘Lead’ task type is converted into a ‘Client’ task type, when a lead is closed & won, for instance.

**5.5.** Go to **Customize** \> **Project settings** (at the bottom) and set the default task to your new task type. You can also set this in **Customize** \> **Task types and templates** and click on the `...` to **Set as default**.  
⚠ Note that, going forward, this will apply to all newly created tasks _and_ subtasks. If you don’t want your subtasks to also be task types, checkout the workaround [here](https://forum.asana.com/t/task-types-to-optionally-apply-to-subtasks/1103759), where you can also vote for this setting to be optional.

# **6. Clean up**

**6.1.** Delete the temporary rule we created in part 3 of this guide.  
**6.2.** If your Single-select status field is in your library, choose to **Remove** it from the project, instead of deleting it! This is the moment of truth - if your **Customize** menu button turns red, it means a rule broke because it was using your single-select field and you didn’t do step 5.3 correctly. Click into the Customize menu to see which rule it is and just take note of it’s name. Add your single-select field back into the project and then go revisit the rule to fix it, now that it will reveal what your single-select field’s options were. Remove your single-select status field from the project again, and if the Customize menu button no longer turns red that means you are good to go!

Only delete your single-select field from the library if you are certain that no one else in your organization is using it. The benefit of deleting your single-select field is that it will also clean up all residual values which you will notice will remain in the task details’ Fields table. You could have manually cleared these values during step 4.3. but there’s no harm in doing this after the main procedure.

If you are using **Sections** , it could be premature to delete them at this stage. You could start using the project with your task types for a few days to make sure all rules are running as expected. Otherwise, if you are confident that NO rules are actioning anything to do with Sections (for example when tasks move from one section to another), then go ahead and delete all Sections, one by one. Obviously choose to keep all tasks and just delete the section. Wait for all tasks to move from the recently deleted section and appear in the next existing section, before deleting the next section. Do this process slowly but steadily as there could be some unexpected behaviour with tasks orphaned from not belonging in a section - it’s happened!

**6.3.** Edit and revise any custom scripts, 3rd-party apps or integrators such as [zapier.com](http://zapier.com) that use your single-select field or Sections, to instead use your custom task type instead. This part could be a bit ‘painful’ but trust me, it will be worth it in the long run.

  

Enjoy your revamped Asana projects with your new custom task types! 💪

  

# **🔗 Resources**

- [🚦 Custom Task types: What you need to know before you go all in](https://forum.asana.com/t/custom-task-types-what-you-need-to-know-before-you-go-all-in/1108888)
- [😱 The Asana feature I wish I’d discovered sooner: Custom Task types](https://forum.asana.com/t/the-asana-feature-i-wish-i-d-discovered-sooner-custom-task-types/1110330)
- [Asana Help Center](https://help.asana.com/s/article/custom-task-types?language=en_US)

  

**[Richard Sather](https://www.richardsather.com/)**  
Asana Solutions Partner & Forum Leader  
🚀 See all of our top tips & tricks on our [website](https://www.richardsather.com/top-tips-tricks).

---

<div class="post-metadata">

**Author:** ![Larry\_Berger\_lpb](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/larry_berger_lpb/32/276017_2.png) [@Larry\_Berger\_lpb](https://forum.asana.com/u/Larry_Berger_lpb)\
**Post date:** [24 November 2025 17:32 UTC](https://forum.asana.com/t/we-replaced-all-our-status-fields-with-task-types-a-guide-on-migrating-your-existing-workflows-to-use-task-types/1110357/2 "2025-11-24T17:32:00Z")

</div>

Terrific step-by-step instructions and great detail for anyone embarking on this kind of change; thanks, @Richard_Sather, for another excellent #Community Tips > Forum Leader tips!

You reference [🚦 Custom Task types: What you need to know before you go all in](https://forum.asana.com/t/custom-task-types-what-you-need-to-know-before-you-go-all-in/1108888) in your Resources here, and I recommend that anyone considering this change read that post closely first to make sure they’re comfortable with the current state of custom task types functionality before they begin using them, either for conversion of existing section or custom field approaches, or for a new usage. There are a few dozen ⚠ and ❌ flags in that post, some of which you may consider gotchas or must-haves.

Thanks,

Larry

---

<div class="post-metadata">

**Author:** ![Richard\_Sather](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/richard_sather/32/276096_2.png) [@Richard\_Sather](https://forum.asana.com/u/Richard_Sather)\
**Post date:** [24 November 2025 20:34 UTC](https://forum.asana.com/t/we-replaced-all-our-status-fields-with-task-types-a-guide-on-migrating-your-existing-workflows-to-use-task-types/1110357/3 "2025-11-24T20:34:17Z")

</div>

Thanks, @Larry_Berger_lpb and you’re absolutely right. That’s why I also referenced that post in the intro of this thread as a ‘proceed with caution’ notice before we get too excited over Custom task types!

---

<div class="post-metadata">

**Author:** ![Bastien\_Siebman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/bastien_siebman/32/172354_2.png) [@Bastien\_Siebman](https://forum.asana.com/u/Bastien_Siebman)\
**Post date:** [27 December 2025 09:57 UTC](https://forum.asana.com/t/we-replaced-all-our-status-fields-with-task-types-a-guide-on-migrating-your-existing-workflows-to-use-task-types/1110357/4 "2025-12-27T09:57:09Z")

</div>

Amazing post, very detailed. Thanks!

---

<div class="post-metadata">

**Author:** ![Richard\_Sather](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/richard_sather/32/276096_2.png) [@Richard\_Sather](https://forum.asana.com/u/Richard_Sather)\
**Post date:** [27 December 2025 10:37 UTC](https://forum.asana.com/t/we-replaced-all-our-status-fields-with-task-types-a-guide-on-migrating-your-existing-workflows-to-use-task-types/1110357/5 "2025-12-27T10:37:46Z")

</div>

Thanks, @Bastien_Siebman ! So are you convinced on migrating to custom task types yet? 😅

---

<div class="post-metadata">

**Author:** ![Bastien\_Siebman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/bastien_siebman/32/172354_2.png) [@Bastien\_Siebman](https://forum.asana.com/u/Bastien_Siebman)\
**Post date:** [27 December 2025 13:16 UTC](https://forum.asana.com/t/we-replaced-all-our-status-fields-with-task-types-a-guide-on-migrating-your-existing-workflows-to-use-task-types/1110357/6 "2025-12-27T13:16:21Z")

</div>

For new projects, why not. We tried once and weren’t convinced. But for all the existing projects: no way. The benefits do not outweigh the cost: we use status fields a lot, with rules, bundles, Script Actions, AI Studio instructions, custom code… it would very risky to migrate

---

<div class="post-metadata">

**Author:** ![Richard\_Sather](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/richard_sather/32/276096_2.png) [@Richard\_Sather](https://forum.asana.com/u/Richard_Sather)\
**Post date:** [27 December 2025 16:52 UTC](https://forum.asana.com/t/we-replaced-all-our-status-fields-with-task-types-a-guide-on-migrating-your-existing-workflows-to-use-task-types/1110357/7 "2025-12-27T16:52:28Z")

</div>

> [@Bastien\_Siebman](#):
>
> For new projects, why not.

That’s good enough for me! 🙂

---

<div class="post-metadata">

**Author:** ![Jan-Rienk](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/jan-rienk/32/227709_2.png) [@Jan-Rienk](https://forum.asana.com/u/Jan-Rienk)\
**Post date:** [27 December 2025 21:38 UTC](https://forum.asana.com/t/we-replaced-all-our-status-fields-with-task-types-a-guide-on-migrating-your-existing-workflows-to-use-task-types/1110357/8 "2025-12-27T21:38:42Z")

</div>

Aha, the scripts make it tricky. For the rest it should be easy enough to see what needs replacing after having deleted the status field. 🤣

---

<div class="post-metadata">

**Author:** ![Bastien\_Siebman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/bastien_siebman/32/172354_2.png) [@Bastien\_Siebman](https://forum.asana.com/u/Bastien_Siebman)\
**Post date:** [28 December 2025 09:44 UTC](https://forum.asana.com/t/we-replaced-all-our-status-fields-with-task-types-a-guide-on-migrating-your-existing-workflows-to-use-task-types/1110357/9 "2025-12-28T09:44:44Z")

</div>

> [@Jan-Rienk](#):
>
> For the rest it should be easy enough to see what needs replacing after having deleted the status field. 🤣

Wrong 🙂 when you break a rule, in some cases, no one is notified. So you have to go through the projects that were using this field. And you have to get that list before removing the field… 🤯

---

<div class="post-metadata">

**Author:** ![Jan-Rienk](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/jan-rienk/32/227709_2.png) [@Jan-Rienk](https://forum.asana.com/u/Jan-Rienk)\
**Post date:** [28 December 2025 09:58 UTC](https://forum.asana.com/t/we-replaced-all-our-status-fields-with-task-types-a-guide-on-migrating-your-existing-workflows-to-use-task-types/1110357/10 "2025-12-28T09:58:35Z")

</div>

You’re right. Most of my setups the logic around a custom field is either in one project or one bundle, so that’s what I had in mind. (and the YOLO approach was in jest I’m sure you realise)

I found your post on finding all broken rules: [Find all broken rules?](https://forum.asana.com/t/find-all-broken-rules/165468), which is one part of the puzzle.

But I saw you suggesting a notification of rules breaking before. Is there already a topic about that?

---

<div class="post-metadata">

**Author:** ![Bastien\_Siebman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/bastien_siebman/32/172354_2.png) [@Bastien\_Siebman](https://forum.asana.com/u/Bastien_Siebman)\
**Post date:** [29 December 2025 07:10 UTC](https://forum.asana.com/t/we-replaced-all-our-status-fields-with-task-types-a-guide-on-migrating-your-existing-workflows-to-use-task-types/1110357/11 "2025-12-29T07:10:29Z")

</div>

> [@Jan-Rienk](#):
>
> I found your post on finding all broken rules: [Find all broken rules?](https://forum.asana.com/t/find-all-broken-rules/165468), which is one part of the puzzle.
> 
> But I saw you suggesting a notification of rules breaking before. Is there already a topic about that?

Not sure if there is a topic but I recently told Julio the PM.

---

<div class="post-metadata">

**Author:** ![Jan-Rienk](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/jan-rienk/32/227709_2.png) [@Jan-Rienk](https://forum.asana.com/u/Jan-Rienk)\
**Post date:** [8 January 2026 15:35 UTC](https://forum.asana.com/t/we-replaced-all-our-status-fields-with-task-types-a-guide-on-migrating-your-existing-workflows-to-use-task-types/1110357/12 "2026-01-08T15:35:40Z")

</div>

There you go: [Notify rule owners of broken rules](https://forum.asana.com/t/notify-rule-owners-of-broken-rules/1117208)

---

<div class="post-metadata">

**Author:** ![ka\_nishiyama](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/ka_nishiyama/32/292165_2.png) [@ka\_nishiyama](https://forum.asana.com/u/ka_nishiyama)\
**Post date:** [6 February 2026 03:32 UTC](https://forum.asana.com/t/we-replaced-all-our-status-fields-with-task-types-a-guide-on-migrating-your-existing-workflows-to-use-task-types/1110357/13 "2026-02-06T03:32:49Z")

</div>

Proliferation of custom task types

I’ve created a custom task type for each project. When converting a multi-homed task, custom task types from different projects are displayed, which is confusing.

Do you have any advice on this?

---

<div class="post-metadata">

**Author:** ![Richard\_Sather](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/richard_sather/32/276096_2.png) [@Richard\_Sather](https://forum.asana.com/u/Richard_Sather)\
**Post date:** [6 February 2026 05:40 UTC](https://forum.asana.com/t/we-replaced-all-our-status-fields-with-task-types-a-guide-on-migrating-your-existing-workflows-to-use-task-types/1110357/14 "2026-02-06T05:40:29Z")

</div>

Hi @ka_nishiyama , I’m not following why you have a different task type per project? Couldn’t it be one task type from your library, applicable to all tasks in these projects?

Otherwise, yes, your task’s ‘convert to’ menu will be packed full of various task types. But even so, that shouldn’t bother you as I would rather have rules in place to automatically convert tasks to a task type upon creation (or set by default if you also want them to set task types to subtasks)

---

<div class="post-metadata">

**Author:** ![ka\_nishiyama](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/ka_nishiyama/32/292165_2.png) [@ka\_nishiyama](https://forum.asana.com/u/ka_nishiyama)\
**Post date:** [6 February 2026 07:25 UTC](https://forum.asana.com/t/we-replaced-all-our-status-fields-with-task-types-a-guide-on-migrating-your-existing-workflows-to-use-task-types/1110357/15 "2026-02-06T07:25:32Z")

</div>

Hi @Richard_Sather

If I were to draw what I see in front of me right now, it would look something like this.  
(although I’ve omitted a lot of details)

 ![{F9EB81D2-6ADF-429D-BDB0-A73052042107}](https://us1.discourse-cdn.com/asana/original/4X/f/2/b/f2bb2d3f204bfe47dc6fe837e99cde55cd807cec.png)

---

<div class="post-metadata">

**Author:** ![Richard\_Sather](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/richard_sather/32/276096_2.png) [@Richard\_Sather](https://forum.asana.com/u/Richard_Sather)\
**Post date:** [6 February 2026 09:38 UTC](https://forum.asana.com/t/we-replaced-all-our-status-fields-with-task-types-a-guide-on-migrating-your-existing-workflows-to-use-task-types/1110357/16 "2026-02-06T09:38:44Z")

</div>

So T1-1 cannot be the same task type as T2-1? 🤔  
I’m not sure we are going to solve this here in the forum, @ka_nishiyama  
The forum is not the ideal medium for such things; I usually do such discovery and solutioning during an interactive online session 🙂

---

<div class="post-metadata">

**Author:** ![ka\_nishiyama](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/ka_nishiyama/32/292165_2.png) [@ka\_nishiyama](https://forum.asana.com/u/ka_nishiyama)\
**Post date:** [6 February 2026 23:52 UTC](https://forum.asana.com/t/we-replaced-all-our-status-fields-with-task-types-a-guide-on-migrating-your-existing-workflows-to-use-task-types/1110357/17 "2026-02-06T23:52:15Z")

</div>

Hi @Richard_Sather

I recently realized that anyone can create their own task types. (Sorry if I’m wrong.)  
If that’s the case, I imagine different task types will be created for each project.

For example,

Type 1: Progress  
-Plan  
-Execute  
-Complete

Type 2: Distinction  
-Task  
-Email  
-Memo  
-Box Address

Should we move this topic to an Ask Question?