Skip to content

DEV - Adding StartDate and EndDate fields to Datepicker #1936

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.

Sign up for GitHub

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

Jump to bottom
Open
4 tasks
ryanfchase opened this issue Feb 20, 2025 · 0 comments
Open
4 tasks

DEV - Adding StartDate and EndDate fields to Datepicker #1936

ryanfchase opened this issue Feb 20, 2025 · 0 comments
Assignees
@ryanfchase
Labels
Complexity: Medium require research/investigation before completing; internal team info/input or external team question draft ticket is still being created, development state p-feature: Search/Filter Modal associated with the Search/Filter Modal for public interaction/viewing ready for dev lead ready for developer lead to review the issue Role: Frontend React front end work size: 3pt Can be done in 13-18 hours
Milestone
Y - Usability and...

Comments

@ryanfchase
Copy link
Member

ryanfchase commented Feb 20, 2025 •
edited
Loading

Overview

We need to make the Datepicker easier to use by adding explicit Start Date and End Date fields, since the previous design left users confused if they were selecting start date or end date.

Action Items

  • Break the issue down into manageable and actionable steps here
  • action 2
  • action 3
  • action 4

Resources/Instructions

[Replace this text - Provide these resources here if exist. Provide screenshot only if the issue has visual
changes on the site, do not post screenshots of codebase]

Screenshot before proposed changes

[insert screenshot here]

Screenshot after proposed changes

[insert screenshot here]

@ryanfchase ryanfchase added Complexity: Missing This ticket needs a complexity (good first issue, small, medium, or large) draft ticket is still being created, development state Feature: Missing missing the appropriate feature association, to which it's related Milestone: Missing without the associated milestone for which it is related attached Role: Frontend React front end work labels Feb 20, 2025
@ryanfchase ryanfchase self-assigned this Feb 20, 2025
@ryanfchase ryanfchase mentioned this issue Feb 20, 2025
Closed
13 tasks
@ExperimentsInHonesty ExperimentsInHonesty added the size: Missing missing the appropriate size that indicates the time/hours it will take to complete label Feb 21, 2025
@github-project-automation github-project-automation bot moved this to New Issue Approval in P: 311: Project Board Feb 21, 2025
@ExperimentsInHonesty ExperimentsInHonesty added p-feature: Search/Filter Modal associated with the Search/Filter Modal for public interaction/viewing and removed Feature: Missing missing the appropriate feature association, to which it's related labels Feb 21, 2025
@ryanfchase ryanfchase added size: 3pt Can be done in 13-18 hours Complexity: Medium require research/investigation before completing; internal team info/input or external team question and removed size: Missing missing the appropriate size that indicates the time/hours it will take to complete Milestone: Missing without the associated milestone for which it is related attached Complexity: Missing This ticket needs a complexity (good first issue, small, medium, or large) labels Feb 23, 2025
@ryanfchase ryanfchase added the ready for dev lead ready for developer lead to review the issue label Mar 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ryanfchase ryanfchase

Labels
Complexity: Medium require research/investigation before completing; internal team info/input or external team question draft ticket is still being created, development state p-feature: Search/Filter Modal associated with the Search/Filter Modal for public interaction/viewing ready for dev lead ready for developer lead to review the issue Role: Frontend React front end work size: 3pt Can be done in 13-18 hours
Projects
P: 311: Project Board
Status: New Issue Approval
Milestone
Y - Usability and Accessibility (Post...
Development

No branches or pull requests
2 participants
@ryanfchase @ExperimentsInHonesty