Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Filter by Date Range #161

Open
seetohjinwei opened this issue Jul 4, 2023 · 2 comments
Open

Filter by Date Range #161

seetohjinwei opened this issue Jul 4, 2023 · 2 comments
Labels

Comments

@seetohjinwei
Copy link
Contributor

Is your feature request related to a problem? Please describe.

There is no way to filter by a date range.

Describe the solution you'd like

Add a date range selector to the filter-bar component to allow for filtering by start and end dates, we could perhaps use the created_at field for the filtering.

An additional feature could be to have a few pre-determined date ranges, like:

  • this week (past 7 days)
  • this month (past 30 days)
  • old (older than 30 days)

The user could select from a dropdown and quickly populate the date range selector.

After adding this date range selector, the filter-bar component might be too cramped on smaller screens (e.g. split screen on a laptop). So, it might be a good idea to split the filter-bar into two rows, if the items in the component become too small.

Describe alternatives you've considered

One possible workaround is to create milestones for each time period. However, this needs to be manually created and the milestones have to be assigned individually to the issues / PRs. Furthermore, this cannot be done within WATcher itself.

Additional context

This might not be super helpful for CS2103 TP teams, but I think it would be useful for larger repositories, and might be worth looking into!

@seetohjinwei seetohjinwei added the category.Feature a new feature label Jul 4, 2023
@damithc
Copy link
Contributor

damithc commented Jul 4, 2023

@seetohjinwei thanks for the feature suggestion.

Let's keep it in our list but for the time being let's limit to features that are useful to CS2103. That will help us keep the product focused on a specific target user, and avoid feature creep.

@seetohjinwei
Copy link
Contributor Author

Got it, thanks prof!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants