Support using object relation type for grouping in Kanbans

Describe Your Request

I think the problem on the product, filtering When selecting a tag, you should choose one of the tags to filter, and only the text is non-empty filtering

Image or Video

This is not very clear.

Hi @rock

Welcome to the Community!

We would like to investigate your issue, but I’m afraid we cannot understand your report.

Could you please share a clearer description of what it is you’re trying to do? A screen-recording would be very helpful as well.

You can write it in your native language and translate it to English with deepL.

Thanks!

The grouping condition of the set only be the label type, and you can also group it with objects

@Bug_Detectives any idea what this is about…? I’m not able to decipher what @rock is trying to communicate.

I’m wracking my brain here, but I think it’s something about the “Is not empty” criteria of the Filter, when applied to Tags, is being influenced by whether or not they have text content?

When he writes “label type” he means in truth “Relation”.

I “translate” his post for you:
The grouping condition of a Set’s View depends only on the Relation, and (but) you can also group it by the Object’s type.

I saw it and tried to figure out what they meant but I couldn’t. Maybe a screen recording of the issue will help convoy the message better.

Addition:
My post wasn’t helpfull. I overlooked that you asked for the startpost, @Angelo
Unfortunately I also can’t get it clear, what he tries to communicate.

@rock please use your native language for this one time.

I suspect OP is talking about set creation. When user already has a relation in function, object type cannot be selected.

@rock Would this be your case scenario (because you said you uploaded a wrong picture in the following post)? Please try deleting the criteria displayed like in the screenshot above, then add your required object type as the filter criteria.

Yes, that’s what I mean, I don’t speak English well so I don’t express myself well. Thank you.

I just realized that I uploaded my picture wrong, and I’m very sorry for the unnecessary trouble, what you understand by grouping by object type is what I wanted to convey

@rock we have here many gentle friends from China, from Russia, and from all over the world.
If you use your native language this time, we’ll surely get it clear what you mean.

Normally this is an English speaking forum. But I suppose in this case it is better when you write in your own tongue this time, instead of using a translator.

(Although using a translator is normally the way to go, they can sometimes make a mess.)

好的,谢谢,我会听取你的意见

人是Tpye类型,我想通过人分组查看set,好像不支持以type类型分组,所以我又多加了一个tag类型的人,这就会导致关联关系比较混乱

What ‘grouping’ are you referring to? 你所指的「分組」是甚麼?

Does the following feature request look like what you want? 下面這個需求是你想要的嗎?

Maybe could you elaborate on your expected behaviour? 可以解釋一下你想達到怎樣的表現嗎?
You could consider making a video to demonstrate. 可以考慮一下用影片的方式呈現你的想法。

I believe I know now what you want.
You want to filter for all “Humans”, correct?

Then this is what you’re looking for:

.

After that, you can add a second filter, for example for a tag.


标记1的是type类型,标记2的是属性类型,我想根据type类型分组,group by选项里没有type类型,所以我就只能多加一遍属性,只是为了实现group by Type

I believe this is a feature request instead of a bug.

OP wants to use object-supported relation as the grouping criteria on kanban board, which Anytype currently only supports tag/checkbox for grouping.

Yes, this should be considered a feature request, and I really like your product, so I’ve been digging into it as well

this is a really important feature!