> If we are filtering for the repo then non-repo related tasks won't be included.

Yes!

> the repo is also used as the root for other non-dev related related activity eg marketing

No. That should ideally be your project's private group or community.

Yes so in order to make parent-based filtering work in theory is to have some "project" kind that is separate from repo kind.

But if we did that, it would be equivalent to having issues and tasks separated.

The benefit I see on the side of having both projects and repos though, is that one project could encompass multiple repos and we don't yet have that afaik.

That would make it useful enough to assign a separate kind and all the non-repo tasks could refer to that instead of the repo as a parent.