add Users to filter options in all list views

[troughc]

Add the Users filter to other workspace List views (in People, Places, Organizations list views)
Same filter as is used in Events

Tasks

Preview Give feedback

1. Add regression test to check if users filter is present in the People, Places, Organizations list views #1483
   +0
   

[AbhishekPAnil]

Estimate : 8H

1. Copy the logic and integration for Users filter from Events listing page into :

• Place -2
• People -2
• Organization -2

2. Testing - 2

[AbhishekPAnil]

@SuhailAliyar
Kindly include support in the Places, People, and Organization listing APIs to retrieve details based on the created user.

[sahalali]

Backend estimate: 2 Hrs

[SyamBabu-M]

@dev-aravind frontend development is complete. Please move this to review after updating staging

[dev-aravind]

@SyamBabu-M There is a small change, the created by param is now changed to created-by instead of user in all pages. Please update the FE to support this.

[SyamBabu-M]

There is a change in frontend after the param name was changed

estimate for this change and testing - 1h

[troughc]

Tested in chrome.
@SyamBabu-M it is working well. One request: can you add any new filter (in this case Users) on a new line the way we do in Events etc. Meaning, the search bar and sorting is on one line and filters are on next line(s). (I have screenshots to show you what I mean)
This should be how it is displayed for filters, including standard andthose set by the admin - this is not the case right now. (see my screenshot of the Organizations list view)

example 1 - events list view

Example 2 - Taxonomies list view with filter on second line

Example 3 is not laid out correctly: Organizations with custom filter and new User filter on first line instead of a new line

[troughc]

Tested: PASSED

[SyamBabu-M]

@troughc Should we wait for the regression test update before going live?

[sahalali]

I don't see any reason for this enhancement to be delayed until the regression tests are complete, as this change will not break any existing regression tests. However, a separate ticket should be created and assigned to Kim for updating the regression tests related to this enhancement.

cc @troughc