Filter on responsible = [me]

beritrep · May 26, 2019, 1:22pm

Hi! I want to set up a view for open actions assigned to the logged-in user only, but I’m not able to find any filter option to select “Responsible” = logged-in user, similar to the = [me] filter in Sharepoint. Is this on the roadmap?

coa · May 27, 2019, 9:32am

Hey @beritrep,

You can filter out the ‘Members’ attribute to be a certain person belonging to your board.

Check out the screenshot:

Let me know if you’ve made it!

beritrep · May 27, 2019, 7:21pm

Sure I can, but if I have 15 members, I’d rather have one view called “my view” than 15 views (one for Alex, one for Betty, one for Catherine…). It would also require me to create a new view every time we change the team. Is it possible with a filter that uses the logged-in user?

BaiJie · May 28, 2019, 1:54am

This was addressed before Here, but it got lost I think. I’m with you! I know that permissions is something in development right now… @coa maybe it is time for a re-visit?

Multiple label type attribute behavior

Yes, that is a good idea for a “dynamic” filter which would be changed based on the signed in user. We already have dynamic filters for dates where you can put “yesterday” for example. In that sense, we could have filter that would say “where member is ME”. The only concern here is whether it will confuse people working on the same view. Imagine having questions on this forum like “my colleagues and I don’t see the same items” :). Great suggestion anyway.

I don’t want to sound like I’m trying to find workarounds for multiple labels issue, but it is possible to split countries into folders, where each folder is a new country. Then you could have one “overview” view on the parent folder which would combine all subfolders.

Private and public views are something we are thinking about from the beginning and it never got a high priority because of how we work as a team. Anyway there is a real need for this kind of features along with permissions.

BaiJie · May 28, 2019, 1:57am

P.S. I think the “Multiple label type attribute behavior” should be revisited as well. I’ll bet a community vote would be heavily in favor of viewing attributes in multiple columns, instead of grouping by unique attribute combinations…

chrish · May 28, 2019, 3:25am

Or being able to choose between “viewing attributes in multiple columns,” or “grouping by unique attribute combinations” so we could have the benefit of using the one that’s most appropriate for the use-case.

BaiJie · May 28, 2019, 4:49am

+1 for configurability. Always!

coa · May 28, 2019, 1:38pm

Thanks @BaiJie for sharing the ‘Multiple label type attribute behavior’ topic.

I’m sure we can revise it As always, peeps, feel free to put your vote and opinion over there.