[UXPROD-2341] Date picker updates Created: 20/Mar/20  Updated: 16/Sep/21  Resolved: 19/Oct/20

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q3 2020

Type: New Feature Priority: P3
Reporter: Khalilah Gambrell Assignee: Khalilah Gambrell
Resolution: Done Votes: 0
Labels: NFR, accessibility, tech-debt, ux
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to STCOM-641 Appropriate Datepicker Calendar local... Closed
relates to STCOM-315 BUG: Datepicker incorrectly manages f... Closed
relates to STCOM-325 Use formField() with <Datepicker> Closed
relates to STCOM-470 FOLIO Calendar Dates issue when in RT... Closed
relates to STCOM-606 Datepicker should update with value p... Closed
relates to STCOM-639 Datepicker submitting localized numer... Closed
relates to STCOM-640 Datepicker RTL mode Closed
relates to STCOM-684 Datepicker - MomentJS defaults to `en... Closed
relates to STCOM-724 Datepicker bugfixes. Closed
relates to STCOM-731 Datepicker losing value on blur Closed
Development Team: Stripes Force
Rank: GBV (MVP Sum 2020): R4

 Description   
  • Address numerous issues with Date picker including
    • Usability
    • Accessibility
    • Localization


 Comments   
Comment by Erin Nettifee [ 06/May/20 ]

Should this be mandatory or NFR? It's in the list of rankings needed for round IV adopters, but I'm not sure how I would prioritize this seems it seems more about underlying functionality rather than features

Comment by Khalilah Gambrell [ 06/May/20 ]

Apologies Erin Nettifee. Added the label NFR.

Comment by Erin Nettifee [ 06/May/20 ]

No worries Khalilah Gambrell thanks for the quick response.

Generated at Fri Feb 09 00:23:09 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.