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

Prevent second order alert is not responding to set threshold not allowing user to confirm

    Details

    • SCRUM Team:
      Brotherhood of Mutants
    • Source Code ID(s):
    • Sprint:
      CFAMX 2019R4 Sprint 1

      Description

      Store : 02693
      TestingENV
      Threshold is set to 1hr
      Dates:

      • DD June 26 08:15am
      • CUD: June 26, 08:15pm +1hm +2hr +3hr and so on, alert never disappears.
      • When user selects the same vendor and same date / time to place order, there's an alert that displays preventing user from creating a second order with message that user must choose another date and/or time greater than 1 hr.
      • However, when user selects hrs greater than 1 hr, alert remain preventing user from moving forward using a different time greater than 1 hr.
      • Workaround, the user had to choose a future date in order to continue to create the order.

      Tested in Staging and it works as designed.

      Dev Note: Rehan looked at this under CFAMX-4476, but it looks like it is not dropping the message after the user has changed the time to be outside of the threshold.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                soma.dixon Soma Dixon (Inactive)
                Reporter:
                will.englefield Will Englefield (Inactive)
              • Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 3h
                  3h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 2.6h Time Not Required
                  2.6h

                    PagerDuty

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