WT RegressionProject Type: business

WT Regression

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

WT -> Transit Regression -> Employer Match Up, Employee Cost fields are not getting saved

    Details

    • Type: Bug
    • Status: Closed
    • Priority: High
    • Resolution: Done
    • Component/s: BenAdmin
    • Labels:
      None
    • Module:
      BenAdmin - Enrollment
    • Reported by:
      Harbinger
    • Item State:
      Production Complete - Closed
    • Issue Importance:
      Can Wait

      Description

      Stage
      ASML for HSPL

      • refer the screen shot attached - cost and coverage for transit plan

      Employer Match Up [flat and percentage], Employee Cost fields are not getting saved

        Attachments

        1. Checklist_WR-67-68.doc
          28 kB
        2. Cust 1.png
          Cust 1.png
          231 kB
        3. WR_67_68_Affected_Files.txt
          1 kB

          Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. WT-10060 WT -> Transit Regression ->cost and coverage set 'Consider previous paid coverage in cost calculation' flag is true, enroll-now screen shown server error.

          • Medium - Has the potential to affect progress.
          • Closed

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            rohit.shete Rohit Shete (Inactive) added a comment -

            WR-67 : WT -> Transit Regression -> Employer Match Up, Employee Cost fields are not getting saved

            Hi Prasad Pise,

            Please find below 3C's:

            Concern: WT -> Transit Regression -> Employer Match Up, Employee Cost fields are not getting saved
            Cause: Code was not present to store Employer Match Up,Employee Cost fields for transit.
            Correction: We have fixed code for this.

            Impact Testing:
            Test FSA and Transit enroll now screens

            Cc: Jyoti Mayne, Alankar Chavan

            Show
            rohit.shete Rohit Shete (Inactive) added a comment - WR-67 : WT -> Transit Regression -> Employer Match Up, Employee Cost fields are not getting saved Hi Prasad Pise , Please find below 3C's: Concern: WT -> Transit Regression -> Employer Match Up, Employee Cost fields are not getting saved Cause : Code was not present to store Employer Match Up,Employee Cost fields for transit. Correction: We have fixed code for this. Impact Testing: Test FSA and Transit enroll now screens Cc: Jyoti Mayne , Alankar Chavan
            Hide
            Permalink
            alankar.chavan Alankar Chavan (Inactive) added a comment -

            This is tested on WT Stage - Working Well

            All the mentioned fields are getting saved

            Actual and assumed expected behavior for these fields are -

            Employer Match Up = 50 %
            Show Employer Coverage = Yes

            say employee puts amount on enroll now screen as 130
            EE cost = 130 / 26 (pay cycle) = 5
            ER Coverage = 65 (130/2)
            ER Cost = 65 / 26 (pay cycle) = 2.5

            This is ready for Stage

            Jyoti Mayne - can you please review mentioned behavior of the system and confirm the same ? Please let us know, if you find any discrepancy in above mentioned scenario

            CC - Sachin Hingole Hrishikesh Deshpande Rakesh Roy Prasad Pise

            Show
            alankar.chavan Alankar Chavan (Inactive) added a comment - This is tested on WT Stage - Working Well All the mentioned fields are getting saved Actual and assumed expected behavior for these fields are - Employer Match Up = 50 % Show Employer Coverage = Yes say employee puts amount on enroll now screen as 130 EE cost = 130 / 26 (pay cycle) = 5 ER Coverage = 65 (130/2) ER Cost = 65 / 26 (pay cycle) = 2.5 This is ready for Stage Jyoti Mayne - can you please review mentioned behavior of the system and confirm the same ? Please let us know, if you find any discrepancy in above mentioned scenario CC - Sachin Hingole Hrishikesh Deshpande Rakesh Roy Prasad Pise
            Hide
            Permalink
            priya.dhamande Priya Dhamande (Inactive) added a comment -

            Environment: Stage
            Company: Asml for Hspl
            Login: Partner and Employee
            Plan: Transit

            Issue: Employer Match Up and Employee Cost fields not getting saved.

            The issue of Employer Match Up and Employee Cost fields not getting saved is verified and is able t save the fields as added

            Impact:
            Added values in fields as:
            Employer Match Up: 70
            Employee Cost fields: 20

            Employee Login > Enroll Now > Transit Plan

            EE Cost: 70/Employee remaining paycycle = 70/12 = 5.83

            As above calculation worked as expected and able to Save the fields, moving jira on Prodution.

            Show
            priya.dhamande Priya Dhamande (Inactive) added a comment - Environment: Stage Company: Asml for Hspl Login: Partner and Employee Plan: Transit Issue: Employer Match Up and Employee Cost fields not getting saved. The issue of Employer Match Up and Employee Cost fields not getting saved is verified and is able t save the fields as added Impact: Added values in fields as: Employer Match Up: 70 Employee Cost fields: 20 Employee Login > Enroll Now > Transit Plan EE Cost: 70/Employee remaining paycycle = 70/12 = 5.83 As above calculation worked as expected and able to Save the fields, moving jira on Prodution.
            Hide
            Permalink
            priya.dhamande Priya Dhamande (Inactive) added a comment - - edited

            Environment: LB
            Company: Asml for Hspl
            Login: Partner and Employee
            Plan: Transit

            Issue: Employer Match Up and Employee Cost fields not getting saved.

            The issue of Employer Match Up and Employee Cost fields not getting saved is verified on LB and is able to save the fields as added.

            Impact:
            checked Employee login with its cost.

            So, moving jira on Stage.

            Show
            priya.dhamande Priya Dhamande (Inactive) added a comment - - edited Environment: LB Company: Asml for Hspl Login: Partner and Employee Plan: Transit Issue: Employer Match Up and Employee Cost fields not getting saved. The issue of Employer Match Up and Employee Cost fields not getting saved is verified on LB and is able to save the fields as added. Impact: checked Employee login with its cost. So, moving jira on Stage.
            Hide
            Permalink
            priya.dhamande Priya Dhamande (Inactive) added a comment - - edited

            Environment: Stage
            Company: Asml for hspl
            Login: Partner and Employee
            Plan Type: Transit

            The issue of Cost and Coverage fields "Employer Match Up" and "Employer Cost" are getting properly saved. also, able to verify corresponding changes with Employee login after enrolling the plan.

            So, moving jira on production.

            Show
            priya.dhamande Priya Dhamande (Inactive) added a comment - - edited Environment: Stage Company: Asml for hspl Login: Partner and Employee Plan Type: Transit The issue of Cost and Coverage fields "Employer Match Up" and "Employer Cost" are getting properly saved. also, able to verify corresponding changes with Employee login after enrolling the plan. So, moving jira on production.
            Hide
            Permalink
            priya.dhamande Priya Dhamande (Inactive) added a comment - - edited

            Environment: Production
            Company: Asml for hspl
            Login: Partner and Employee
            Plan Type: Transit

            The issue of Cost and Coverage fields "Employer Match Up" and "Employer Cost" are getting saved is resolved on Production. Verified the same on mentioned company. So, closing jira on production.

            Show
            priya.dhamande Priya Dhamande (Inactive) added a comment - - edited Environment: Production Company: Asml for hspl Login: Partner and Employee Plan Type: Transit The issue of Cost and Coverage fields "Employer Match Up" and "Employer Cost" are getting saved is resolved on Production. Verified the same on mentioned company. So, closing jira on production.

              People

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

                Dates

                Created:
                Updated:
                Resolved:
                Dev Due Date:
                Code Review Date:

                  Time Tracking

                  Estimated:
                  Original Estimate - 16h Original Estimate - 16h
                  16h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 22h
                  22h