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

Change the default date range for all filters to 60 days prior, 30 days in the future. #4740

Closed
4 tasks
cielf opened this issue Oct 27, 2024 · 2 comments · Fixed by #4752
Closed
4 tasks
Assignees

Comments

@cielf
Copy link
Collaborator

cielf commented Oct 27, 2024

Summary

Change the default date range for all filters to 60 days prior, 30 days in the future.

Why

The current date range of "current year" does not return the things that are of interest in the first part of the year, and returns far more than is useful in the second half of the year. Note: We have checked the proposed date range with the stakeholder circle.

Details

There are many places this is used in the system. Here is a path to one of them:
log in as org_admin1@example.com. Click "Distributions" in the left-hand menu.

Add a new described range to the available date ranges -- "Default" -- which is 60 days prior, 30 days in the future
Default all the date range filters to that date range

Criteria for completion

  • additional filter date range as described
  • all filters defaulted to that (This is probably all done in one place in the code)
  • tests for additional date range
  • current tests adapted to allow for new default date range
@cielf cielf added Help Wanted Groomed + open to all! Difficulty—Beginner labels Oct 27, 2024
@jorgecoutinhobr
Copy link
Contributor

I would like to work on this issue. It appears to be a continuation of the issue that i worked on 😁

@cielf
Copy link
Collaborator Author

cielf commented Oct 29, 2024

It's certainly related!

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

Successfully merging a pull request may close this issue.

2 participants