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

Angular Update > Implement session Timeout

    Details

    • Sprint:
      CFAMX Angular Update Sprint 2, CFAMX Angular Update Sprint 3, 2021.R3 Angular-2 Sprint 1, 2021.R3 Angular-2 Sprint 2, 2021.R3 Angular-2 Sprint 3
    • SCRUM Team:
      Brotherhood of Mutants
    • Story Points:
      3
    • Work Type Classification:
      Sustaining

      Description

      AC - Implement Session Timeout
      it should work as described in the JIRA ticket was done for MxConnect:
      https://jira.hotschedules.com/browse/CFAMX-11370

      AC - the System should be Reinstated if the site becomes online from offline mode.

      Confirm:
      In the Chrome Network tab select offline: then you should get backplane that is not an active message in the console. No popups should be displayed.
      When an online mode is selected after ~20 seconds you should see a popup that you can either refresh the site or hit cancel.

        Attachments

        1. screenshot-1.png
          screenshot-1.png
          107 kB
        2. screenshot-2.png
          screenshot-2.png
          15 kB
        3. screenshot-3.png
          screenshot-3.png
          56 kB
        There are no Sub-Tasks for this issue.

          Activity

            People

            • Assignee:
              jason.powell Jason Powell
              Reporter:
              Gareth.Leibbrandt Gareth Leibbrandt (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 31.5h
                31.5h
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 22h 31m Time Not Required
                22h 31m

                  PagerDuty

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