Uploaded image for project: 'WT Regression'
  1. WT Regression
  2. WR-66

WT -> Life Regression - > Cases which did not work in case of core plan allocation effetcive date rules

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Medium
    • Resolution: Done
    • Component/s: BenAdmin
    • Labels:
      None
    • Bug Type:
      Functional
    • Level:
      Admin, Employee, Partner
    • Module:
      BenAdmin - Enrollment
    • Reported by:
      Harbinger
    • Issue Importance:
      Can Wait

      Description

      WT Stage
      Valmet Benefits

      Case 1:

      employee ineligible to core plan
      no mode active
      QE raised 01st July - made employee eligible by changing his demographic details
      expected results - employee should be auto enrolled in the plan plan from 30th July 2016 (company level eff date rule - end of month)
      actual results - employee did not get auto enrolled in the plan only

      Case 2:

      employee ineligible to core plan
      no mode active
      date of employment - 07/01/2015
      QE raised 26th July 2016 - made employee eligible by changing his demographic details
      rule for newly eligible core plan at plan level is use waiting period - first of month following date of change
      expected results - employee should be auto enrolled in the plan plan from 01 August 2016
      actual results - employee did not get auto enrolled in the plan only
      Also did not work for new hire rule - use waiting period - first of month following date of Hire

      Case 3:

      employee ineligible to core plan
      no mode active
      QE raised 15th July 2016 - made employee eligible by changing his demographic detail
      rule for newly eligible core plan at plan level is use waiting period - XX days before date of change : xx= 30
      expected results - employee should be auto enrolled in the plan plan from 15th June 2016
      actual results - employee got auto enrolled in the plan with date of change only
      tested this multiple times with various XX values

      Case 4:

      employee ineligible to core plan
      no mode active
      QE raised 15th July 2016 - made employee eligible by changing his demographic detail
      rule for newly eligible core plan at plan level is first of month following or coincident with date of change
      expected results - employee should be auto enrolled in the plan plan from 01st Aug 2016
      actual results - employee did not get auto enrolled in the plan only
      Also did not work for new hire rule -first of month following or coincident with date hire

        Attachments

          Activity

          Hide
          jyoti.mayne Jyoti Mayne added a comment -

          Hi Amruta Lohiya,

          There seems to be problem in core plan allocation effective date calculation. We need time to analysis this issue first and then will convey LB due Date for same.

          Show
          jyoti.mayne Jyoti Mayne added a comment - Hi Amruta Lohiya , There seems to be problem in core plan allocation effective date calculation. We need time to analysis this issue first and then will convey LB due Date for same.
          Hide
          jyoti.mayne Jyoti Mayne added a comment -

          Hi Prasad Pise,

          Could you please go thorough above scenarios and check if issue still exists?

          Cc: Satya, Vijay Siddha, Gaurav Sodani

          Show
          jyoti.mayne Jyoti Mayne added a comment - Hi Prasad Pise , Could you please go thorough above scenarios and check if issue still exists? Cc: Satya , Vijay Siddha , Gaurav Sodani
          Show
          prasadp Prasad Pise (Inactive) added a comment - cc: Hrishikesh Deshpande Sachin Hingole Rakesh Roy
          Hide
          hrishikesh.deshpande Hrishikesh Deshpande (Inactive) added a comment -

          We will plan this on 08/28.

          Show
          hrishikesh.deshpande Hrishikesh Deshpande (Inactive) added a comment - We will plan this on 08/28.
          Hide
          priya.dhamande Priya Dhamande (Inactive) added a comment -

          Scenario 1 : verified
          This issue is resolved.

          Testing in progress.

          Hrishikesh Deshpande

          Show
          priya.dhamande Priya Dhamande (Inactive) added a comment - Scenario 1 : verified This issue is resolved. Testing in progress. Hrishikesh Deshpande
          Hide
          priya.dhamande Priya Dhamande (Inactive) added a comment -

          Scenario 1, 2 and 3 are verified on Production. All scenarios worked as expected. So, closing jira.

          Show
          priya.dhamande Priya Dhamande (Inactive) added a comment - Scenario 1, 2 and 3 are verified on Production. All scenarios worked as expected. So, closing jira.
          Hide
          priya.dhamande Priya Dhamande (Inactive) added a comment -

          These scenarios are already implemented.

          Show
          priya.dhamande Priya Dhamande (Inactive) added a comment - These scenarios are already implemented.

            People

            Assignee:
            priya.dhamande Priya Dhamande (Inactive)
            Reporter:
            alankar.chavan Alankar Chavan (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 10h
                10h
                Remaining:
                Time Spent - 4.5h Remaining Estimate - 5.5h
                5.5h
                Logged:
                Time Spent - 4.5h Remaining Estimate - 5.5h
                4.5h