Uploaded image for project: 'CFA MX '
  1. CFA MX
  2. CFAMX-2732

2019.R2(S4):Correct Validation around the forced Date/Time Fields when applying counts

    Details

    • Type: Sprint Defect
    • Status: Done (View Workflow)
    • Priority: Major
    • Resolution: Completed
    • Affects Version/s: CFA 2019R2
    • Fix Version/s: CFA 2019R2
    • Component/s: Counting
    • Labels:
      None
    • SCRUM Team:
      Brotherhood of Mutants
    • Source Code ID(s):
    • Sprint:
      CFAMX 2019R2 Sprint 5

      Description

      1. The warning message seems to warn the user when the date is in the future, but not the time (Can we change the validation of this field and make it highlighted in red, when the date or time is in the future). This behavior would be similar to other fields in MxConnect, but not how the existing modals work.  This would be a new standard going forward.
      2. Currently, the user can enter a future time, even though a future date is not permitted. Disable the button when a future date and or time is selected as it works today in 2019.R1.
      3. Can we remove the Weeks from the calendar in the modal?   cc: Staten Putnal  Will Englefield  Michael DeBinder

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                soma.dixon Soma Dixon (Inactive)
                Reporter:
                soma.dixon Soma Dixon (Inactive)
              • Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 2h Original Estimate - 2h
                  2h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 4h
                  4h

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.