human-essentials icon indicating copy to clipboard operation
human-essentials copied to clipboard

Add "prior year" to the date range drop downs

Open cielf opened this issue 1 year ago • 9 comments

Summary

Add "prior year" to the date range drop downs throughout.

Why?

In January, a lot of people are trying to get information about the year before. They very often are not entering the date range correctly, which causes exceptions

Details

The prior year range should be January 1 - December 31 of the calendar year preceding the current calendar year. i.e. in 2024 it would be January 1 2023 - December 31 2023. I suggest that you can likely use the "this year" selection as a model.

This might conflict with the Dashboard change that is coming in in the next few weeks at time of writing (January 2024). Be aware of that.

Criteria for completion

  • [ ] The year range exists and is available on all the reports/indices that use date range filtering
  • [ ] Tests to demonstrate the change

cielf avatar Feb 04 '24 16:02 cielf

Is this issue still open? Would love to take it

Gabe-Torres avatar Apr 07 '24 03:04 Gabe-Torres

Hey @Gabe-Torres, it's technically open, but blocked by a PR that's currently in review. @awwaiid -- would it make sense for @Gabe-Torres to take this on branching off of the Dashboard branch?

cielf avatar Apr 07 '24 17:04 cielf

No longer blocked -- Dashboard has been merged into main.

cielf avatar May 26 '24 13:05 cielf

Hi @cielf, could I try taking this one on?

noah-puckett avatar Jul 03 '24 16:07 noah-puckett

Sure!

cielf avatar Jul 03 '24 16:07 cielf

Currently a bit blocked due to codespaces no longer working for me, due to getting failed javascript runtime errors as described in this PR.

noah-puckett avatar Jul 10 '24 16:07 noah-puckett

Currently a bit blocked due to codespaces no longer working for me, due to getting failed javascript runtime errors as described in this PR.

For now you can run nvm install node followed by rbenv init in the shell of your choice and that should resolve the error until the PR gets merged

jimmyli97 avatar Jul 10 '24 23:07 jimmyli97

This issue is marked as stale due to no activity within 30 days. If no further activity is detected within 7 days, it will be unassigned.

github-actions[bot] avatar Aug 10 '24 00:08 github-actions[bot]

Automatically unassigned after 7 days of inactivity.

github-actions[bot] avatar Aug 18 '24 00:08 github-actions[bot]