Open Jayden-Kim-NUS opened 1 week ago
Thanks for reporting this issue! The lack of a filtering feature for meetings means users may need to manually scroll or visually scan to find the desired meeting. We think that this is a minor inconvenience that does not impact the usability of the product because for most users, the number of meetings they need to manage in a fixed time period (e.g. in the upcoming week) will likely be small compared to the number of properties and clients they have. Moreover, while filtering meetings may improve convenience for users, its absence does not hinder users from completing their tasks. Meetings can still be navigated, viewed, and managed using the existing UI or other available commands.
We implemented the filterclient
command as property agents have to manage a large database of clients, where filtering by attributes such as name or phone number is critical for operational efficiency. Meetings, on the other hand, are typically fewer in number, so we did not find that a command to filter meetings was a core part of ClientGrid's functionality as of v1.6. The primary goal of the meeting management feature is to ensure that meetings can be created, viewed, and deleted effectively. Filtering is a secondary enhancement that could be considered for future iterations and is not in scope for ClientGrid v1.6.
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
The command to filter clients,
filterclient
, is extremely useful for real estate agents, the same functionality can be extended to meetings.A command like
filtermeeting
will be useful for agents as well as they might need to attend many meetings and need to filter them by date or name or phone number