Uploaded image for project: 'WORKTERRA'
  1. WORKTERRA
  2. WT-7182

JE DUNN - QE event ran and it termed HSA election.

    Details

    • Type: Bug
    • Status: Production Complete
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: BenAdmin
    • Labels:
      None
    • Environment:
      Production
    • Module:
      BenAdmin - Enrollment
    • Reported by:
      Support
    • Company:
      JE Dunn
    • Item State:
      Production QA - Production Deployed
    • Issue Importance:
      Must Have

      Description

      JE Dunn EE Lucas Godwin, had a QE of birth of a child and his HSA enrollment termed. In View History it appears as though Anne termed that enrollment but she confirmed she did not waive that benefits.

        Attachments

        1. Enroll now screen.png
          249 kB
          Rashmita Dudhe
        2. JEDunn_ViewHistory.png
          269 kB
          Rashmita Dudhe
        3. JEDunn_ViewHistory.png
          269 kB
          Rashmita Dudhe
        4. Enroll now screen.png
          249 kB
          Rashmita Dudhe
        5. Core plan.png
          212 kB
          Rashmita Dudhe
        6. screenshot-1.png
          21 kB
          Tracy Kot
        7. screenshot-2.png
          34 kB
          Tracy Kot

          Activity

          Hide
          rakeshr Rakesh Roy (Inactive) added a comment -

          Rashmita Dudhe Please check and confirm.

          Show
          rakeshr Rakesh Roy (Inactive) added a comment - Rashmita Dudhe Please check and confirm.
          Hide
          rashmita.dudhe Rashmita Dudhe (Inactive) added a comment -

          As per you mention Above i have verified below scenarios On Production Environment:
          Scenarios 1: (Verified Through UI Import)Eligibility Contingency :Retro tier Increase
          1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per eligibility contingency rule HSA plan Is eligible to employee and Employee Enrolled in 2016 HSA plan with effective date 01/01/2016
          2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan.
          3]Employee Raised QE with Effective date 12/01/2016 And Increase tier 2017 HSA plan is not terminated.

          Scenarios 2: Eligibility Contingency :Waived parent Plan all Child plan is terminated
          1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per eligibility contingency rule HSA plan Is eligible to employee and Employee Enrolled in 2016 HSA plan with effective date 01/01/2016
          2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan.
          3]Employee Raised QE with Effective date 12/01/2016 And Increase tier 2017 HSA plan is not terminated.
          4]Waived Medical plan the Both HSA 2016 and HSA 2017 Plan are terminated

          Scenarios 3:(Verified Through UI Import)Eligibility Contingency :Future tier Increase
          1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per eligibility contingency rule HSA plan Is eligible to employee and Employee Enrolled in 2016 HSA plan with effective date 01/01/2016
          2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan.
          3]Employee Raised QE with Effective date 03/01/2016 And Increase tier 2017 Medical plan HSA plan Is not Impacted.

          Scenarios 4: (Verified Through UI Import) Forced Contingency :Retro tier Increase
          1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per Forced contingency rule Employee Enrolled In 2016 HSA plan automatically with effective date 01/01/2016
          2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan.
          3]Employee Raised QE with Effective date 12/01/2016 And Increase tier 2017 HSA plan is not terminated.

          Scenarios 5: Forced Contingency :Waived parent Plan all Child plan is terminated
          1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per Forced contingency rule Employee Enrolled In 2016 HSA plan automatically with effective date 01/01/2016
          2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan.
          3]Employee Raised QE with Effective date 12/01/2016 And Increase tier 2017 HSA plan is not terminated.
          4]Waived Medical plan the Both HSA 2016 and HSA 2017 Plan are terminated

          Scenarios 6:(Verified Through UI Import)Forced Contingency :Future tier Increase
          1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per Forced contingency rule Employee Enrolled In 2016 HSA plan automatically with effective date 01/01/2016
          2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan.
          3]Employee Raised QE with Effective date 03/01/2016 And Increase tier 2017 Medical plan HSA plan Is not Impacted.

          all scenarios are working fine as expected

          Show
          rashmita.dudhe Rashmita Dudhe (Inactive) added a comment - As per you mention Above i have verified below scenarios On Production Environment: Scenarios 1: (Verified Through UI Import)Eligibility Contingency :Retro tier Increase 1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per eligibility contingency rule HSA plan Is eligible to employee and Employee Enrolled in 2016 HSA plan with effective date 01/01/2016 2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan. 3]Employee Raised QE with Effective date 12/01/2016 And Increase tier 2017 HSA plan is not terminated. Scenarios 2: Eligibility Contingency :Waived parent Plan all Child plan is terminated 1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per eligibility contingency rule HSA plan Is eligible to employee and Employee Enrolled in 2016 HSA plan with effective date 01/01/2016 2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan. 3]Employee Raised QE with Effective date 12/01/2016 And Increase tier 2017 HSA plan is not terminated. 4]Waived Medical plan the Both HSA 2016 and HSA 2017 Plan are terminated Scenarios 3:(Verified Through UI Import)Eligibility Contingency :Future tier Increase 1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per eligibility contingency rule HSA plan Is eligible to employee and Employee Enrolled in 2016 HSA plan with effective date 01/01/2016 2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan. 3]Employee Raised QE with Effective date 03/01/2016 And Increase tier 2017 Medical plan HSA plan Is not Impacted. Scenarios 4: (Verified Through UI Import) Forced Contingency :Retro tier Increase 1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per Forced contingency rule Employee Enrolled In 2016 HSA plan automatically with effective date 01/01/2016 2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan. 3]Employee Raised QE with Effective date 12/01/2016 And Increase tier 2017 HSA plan is not terminated. Scenarios 5: Forced Contingency :Waived parent Plan all Child plan is terminated 1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per Forced contingency rule Employee Enrolled In 2016 HSA plan automatically with effective date 01/01/2016 2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan. 3]Employee Raised QE with Effective date 12/01/2016 And Increase tier 2017 HSA plan is not terminated. 4]Waived Medical plan the Both HSA 2016 and HSA 2017 Plan are terminated Scenarios 6:(Verified Through UI Import)Forced Contingency :Future tier Increase 1]Employee enrollment In Medical plan with Effective date 01/01/2016 as per Forced contingency rule Employee Enrolled In 2016 HSA plan automatically with effective date 01/01/2016 2]In OE 01/01/2017 Employee Enrolled in to the 2017 Hsa plan. 3]Employee Raised QE with Effective date 03/01/2016 And Increase tier 2017 Medical plan HSA plan Is not Impacted. all scenarios are working fine as expected
          Hide
          rashmita.dudhe Rashmita Dudhe (Inactive) added a comment -

          Hi Tracy Kot,

          This issue was Existing and was resolved with this patch.

          We have verified mention scenarios by adding employee with same customization.
          and the issue is not existing as this is resolved with patch.

          The mentioned issue came before the patch deployment on production.
          Henceforth this issue will not replicate.

          Thanks,
          Rashmita

          Show
          rashmita.dudhe Rashmita Dudhe (Inactive) added a comment - Hi Tracy Kot , This issue was Existing and was resolved with this patch. We have verified mention scenarios by adding employee with same customization. and the issue is not existing as this is resolved with patch. The mentioned issue came before the patch deployment on production. Henceforth this issue will not replicate. Thanks, Rashmita
          Hide
          Tkot Tracy Kot (Inactive) added a comment -

          Rashmita Dudhe, thank you. If this resolved now and in production?

          Show
          Tkot Tracy Kot (Inactive) added a comment - Rashmita Dudhe , thank you. If this resolved now and in production?
          Hide
          rashmita.dudhe Rashmita Dudhe (Inactive) added a comment -

          Hi Tracy Kot,

          This patch is deployed and verified on Production.
          Kindaly, Update Jira accordingly.

          Thanks,
          Rashmita

          Show
          rashmita.dudhe Rashmita Dudhe (Inactive) added a comment - Hi Tracy Kot , This patch is deployed and verified on Production. Kindaly, Update Jira accordingly. Thanks, Rashmita

            People

            Assignee:
            Tkot Tracy Kot (Inactive)
            Reporter:
            Tkot Tracy Kot (Inactive)
            Account Executive:
            Tracy Kot (Inactive)
            Developer:
            Neelam Yangal (Inactive)
            QA:
            Rashmita Dudhe (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 48h Original Estimate - 48h
                48h
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 48.25h
                48.25h