Multihomed subtasks not properly recognized as parent task in multihomed project

English Forum Product Feedback
, ,
1

Consider the following scenario:

  • Project A
    • Task 1
      • Subtask 1.1

Let’s say you want to multihome Subtask 1.1 into a Project B. For example:

  • Project A
    • Task 1
      • Subtask 1.1
  • Project B
    • Subtask 1.1 ← Now a parent-level task in this project

Historically, Subtask 1.1 would now be a parent task in Project B and a subtask in Project A.

:warning: Issue

However, that appears to now not be the case because Subtask 1.1 will no longer display the Project custom field in board view (despite it displaying in List view). Meaning, there is no BoardCardProjectPills-potPillButton within the card div at all.

It shows up as a parent task. It displays the project in the list view. But something fundamental has changed and it is affecting other apps I use downstream because they do not recognize the subtask as a parent task in the multihomed project.

I’ll follow up later with more info after I test things via the API to see what changed.

This has broken my day-to-day workflow. The only workaround I know of right now is to make the subtask both a subtask and a parent task in its primary project before multihoming it to another project.

Which puts me right back where I was like 3 years ago where I had to use Flowsana to multihome every subtask as a parent task in its own parent’s project and make a custom section just for subtasks in every project so the subtasks didn’t clutter everything up. :man_facepalming:

Subtasks now show parent project and fields in the task pane ✨
2

Hi @Skyler,

While I would love for you to need Flowsana :wink:, I’m either not understanding your plight or not seeing the same thing. I tested this in the UI and also checking the underlying object data and am not seeing any issues. But I may not be understanding…

When I replicate multihoming Subtask 1.1 into a Project B , that project shows in the task’s memberships and projects properties just like it always has. And in Board view for Project B, I’m not seeing anything missing that I’m aware of that was present in the past, although I’m not 100% sure what you mean by

(noting also that ‘Project’ is not a custom field).

What am I missing, or are we seeing two different sets of things?

3

Don’t worry @Phil_Seeman there are still plenty of other reasons for me to use Flowsana than just this haha. It still handles my dwell time logic, tagging logic, etc. I just thought I was past the days of auto-promoting every subtask. :rofl:

I checked the API yesterday and also saw it’s membership and projects are still like they were before…so now I’m just confused. There are two main issues I’m experiencing with it currently:

  1. It’s impacting my rules in some projects that shouldn’t be triggering on subtasks.
  2. It’s impacting my 3rd-party integrations that have filter logic related to subtasks (e.g. Sunsama).

They may each be independent issues, though. I’m working on replicating some in my own internal tools to see if I can isolate it.

The other issue related to the project field not showing on the card was me forgetting it never did that before for subtasks and instead just displayed the parent task line (❶ in the figure below) and a task had to be a parent task in a project for the pill to display (❷ in the figure below).

2026.05.28 20.43.42 WRK
2026.05.28 20.43.42 WRK2268×937 197 KB

My project pills display above the task name in the card view and not inline with the other fields because that’s where I think they should display. Makes it easier for me to scan and know what I’m looking at.

1 Like
4

As noted in another forum thread that you commented on, @Richard_Sather is experiencing this, too, so I think it’s real thing. It seems like it must be some internal Asana code change that is essentially bypassing the data model and implementing some new and different behavior.

As you’re probably already thinking, this one is more puzzling since one would think a third-party would just be working off of the API and data model, which as we both agree hasn’t changed.

:grin: :folded_hands:

5

Thank you for flagging this, @Skyler and @Phil_Seeman!

Reading through, it looks like the open issue has focused on a couple of things: Rules firing on subtasks in projects where they previously wouldn’t (which @Richard_Sather appears to be hitting as well), and I see this is also affecting integrations that filter on subtask status.

We’re looking into it now and have flagged the details here to the product team. We’ll follow up in this thread once we understand what’s changed and why. Thanks again!

4 Likes