New Features 2017Project Type: software

New Features 2017

Uploaded image for project: 'New Features 2017'
  1. New Features 2017
  2. NF-4982

Employee did not get Force plan Sequence on QE raise

    Details

    • Type: Bug
    • Status: Production Complete
    • Priority: Medium
    • Resolution: Bug Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: UI Refresh
    • Labels:
      None
    • Environment:
      Others
    • Bug Type:
      Functional
    • Bug Severity:
      Critical
    • Level:
      Employee
    • Module:
      BenAdmin - Enrollment
    • Reported by:
      Harbinger
    • Company:
      City of Bellevue
    • Item State:
      Stage QA - Production Deployment on Hold
    • Browser:
      Google Chrome

      Description

      Pre-requisite-
      1.OE is going on
      2.EE with Employment Date - 01/01/2017
      3.Company Name - For QA-City of Bellevue-Azure

      Step:-
      1.Login with EE credential
      2.Start OE work flow
      3.Navigate to Enroll Now page
      4.Enrolled into plans
      5.Complete Enrollment Tunnel
      6.EE redirect to dashboard
      7.Now raise QE for Marriage - 11/07/2017
      8.QE flow started
      9.Navigate to Enroll Now

      Actual - Application show all plans on Enroll Now screen

      Expected - Force sequence should display on Enroll Now screen.

        Attachments

          Issue Links

          is caused by

          Change Request - Change Request NF-4920 Functional - Any company - EE OE - Same session after completion not able to open up the benefit types.

          • Medium - Has the potential to affect progress.
          • Resolution Setting

            Activity

            Ascending order - Click to sort in descending order
            mahendra.mungase Mahendra Mungase (Inactive) created issue -
            mahendra.mungase Mahendra Mungase (Inactive) made changes -
            Field Original Value New Value
            Link This issue is caused by NF-4920 [ NF-4920 ]
            mahendra.mungase Mahendra Mungase (Inactive) made changes -
            Description Pre-requisite-
            1.OE is going on
            2.EE with Employment Date - 01/01/2017

            Step:-
            1.Login with EE credential
            2.Start OE work flow
            3.Navigate to Enroll Now page
            4.Enrolled into plans
            5.Complete Enrollment Tunnel
            6.EE redirect to dashboard
            7.Now raise QE for Marriage - 11/07/2017
            8.QE flow started
            9.Navigate to Enroll Now

            Actual - Application show all plans on Enroll Now screen

            Expected - Force sequence should display on Enroll Now screen.             		Pre-requisite-
            1.OE is going on
            2.EE with Employment Date - 01/01/2017
            3.Company Name - For QA-City of Bellevue-Azure

            Step:-
            1.Login with EE credential
            2.Start OE work flow
            3.Navigate to Enroll Now page
            4.Enrolled into plans
            5.Complete Enrollment Tunnel
            6.EE redirect to dashboard
            7.Now raise QE for Marriage - 11/07/2017
            8.QE flow started
            9.Navigate to Enroll Now

            Actual - Application show all plans on Enroll Now screen

            Expected - Force sequence should display on Enroll Now screen.
            rohan.khandave Rohan J Khandave (Inactive) made changes -
            Status Open [ 1 ] In Development [ 10007 ]
            rohan.khandave Rohan J Khandave (Inactive) made changes -
            Item State Parent values: Development(10200)Level 1 values: In Progress(10206)
            Hide
            Permalink
            rohan.khandave Rohan J Khandave (Inactive) added a comment -

            Hello Mahendra Mungase,

            Now we will force user as per mode means once user completed tunnel for OE / QE and goes into tunnel again into same session then we will not force sequence. But as per your scenario if OE completed and then raised QE event then we force sequence for QE.

            Thanks,
            RohanK

            CC – Sachin Hingole

            Show
            rohan.khandave Rohan J Khandave (Inactive) added a comment - Hello Mahendra Mungase , Now we will force user as per mode means once user completed tunnel for OE / QE and goes into tunnel again into same session then we will not force sequence. But as per your scenario if OE completed and then raised QE event then we force sequence for QE. Thanks, RohanK CC – Sachin Hingole
            Permalink
            rohan.khandave Rohan J Khandave (Inactive) logged work - 07/Nov/17 02:52 PM
            • Time Spent:
              4h
               
              <No comment>
            rohan.khandave Rohan J Khandave (Inactive) made changes -
            Item State Parent values: Development(10200)Level 1 values: In Progress(10206) Parent values: Development(10200)Level 1 values: Ready for Local Testing(10209)
            Hide
            Permalink
            rohan.khandave Rohan J Khandave (Inactive) added a comment -

            Please check after codemap deployment.

            Show
            rohan.khandave Rohan J Khandave (Inactive) added a comment - Please check after codemap deployment.
            rohan.khandave Rohan J Khandave (Inactive) made changes -
            Assignee Rohan J Khandave [ rohan.khandave ] Mahendra Mungase [ mahendra.mungase ]
            sachin.hingole Sachin Hingole (Inactive) made changes -
            Status In Development [ 10007 ] Local Testing [ 10200 ]
            rohan.khandave Rohan J Khandave (Inactive) made changes -
            Remaining Estimate 16h [ 57600 ]
            Original Estimate 16h [ 57600 ]
            rohan.khandave Rohan J Khandave (Inactive) made changes -
            Remaining Estimate 16h [ 57600 ] 12h [ 43200 ]
            Time Spent 4h [ 14400 ]
            Worklog Id 90263 [ 90263 ]
            Hide
            Permalink
            meghana.joshi Meghana Joshi (Inactive) added a comment -

            Verified on CodeMap through Employee Login
            Working Fine

            CC - Sachin Hingole

            Show
            meghana.joshi Meghana Joshi (Inactive) added a comment - Verified on CodeMap through Employee Login Working Fine CC - Sachin Hingole
            Permalink
            meghana.joshi Meghana Joshi (Inactive) logged work - 13/Nov/17 01:04 PM
            • Time Spent:
              1.5h
               

              Testing on CodeMap

            meghana.joshi Meghana Joshi (Inactive) made changes -
            Remaining Estimate 12h [ 43200 ] 10.5h [ 37800 ]
            Time Spent 4h [ 14400 ] 5.5h [ 19800 ]
            Worklog Id 90484 [ 90484 ]
            khandu.kshirsagar Khandu Kshirsagar (Inactive) made changes -
            Item State Parent values: Development(10200)Level 1 values: Ready for Local Testing(10209) Parent values: LB QA(10201)Level 1 values: LB Deployed(11600)
            sachin.hingole Sachin Hingole (Inactive) made changes -
            Item State Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) Parent values: LB QA(10201)Level 1 values: Ready for Stage(10213)
            sachin.hingole Sachin Hingole (Inactive) made changes -
            Item State Parent values: LB QA(10201)Level 1 values: Ready for Stage(10213) Parent values: LB QA(10201)Level 1 values: In Testing(10210)
            mahendra.mungase Mahendra Mungase (Inactive) made changes -
            Item State Parent values: LB QA(10201)Level 1 values: In Testing(10210) Parent values: LB QA(10201)Level 1 values: On Hold(10211)
            sachin.hingole Sachin Hingole (Inactive) made changes -
            Status Local Testing [ 10200 ] Stage Testing [ 10201 ]
            sachin.hingole Sachin Hingole (Inactive) made changes -
            Item State Parent values: LB QA(10201)Level 1 values: On Hold(10211) Parent values: Stage QA(10202)Level 1 values: Production Deployment on Hold(10224)
            sachin.hingole Sachin Hingole (Inactive) made changes -
            Status Stage Testing [ 10201 ] In Production Testing [ 10202 ]
            sachin.hingole Sachin Hingole (Inactive) made changes -
            Resolution Bug Fixed [ 10402 ]
            Status In Production Testing [ 10202 ] Production Complete [ 10028 ]
            Transition Time In Source Status Execution Times
            Rohan J Khandave (Inactive) made transition -
            Open In Development
            		4h 5m 1
            Sachin Hingole (Inactive) made transition -
            In Development In LB Testing
            		2d 21h 33m 1
            Sachin Hingole (Inactive) made transition -
            In LB Testing Stage Testing
            		67d 3h 50m 1
            Sachin Hingole (Inactive) made transition -
            Stage Testing In Production Testing
            		99d 5h 14m 1
            Sachin Hingole (Inactive) made transition -
            In Production Testing Production Complete
            		4m 50s 1

              People

              Assignee:
              mahendra.mungase Mahendra Mungase (Inactive)
              Reporter:
              mahendra.mungase Mahendra Mungase (Inactive)
              Developer:
              Rohan J Khandave (Inactive)
              QA:
              Mahendra Mungase (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 16h
                  16h
                  Remaining:
                  Time Spent - 5.5h Remaining Estimate - 10.5h
                  10.5h
                  Logged:
                  Time Spent - 5.5h Remaining Estimate - 10.5h
                  5.5h