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

"Rehire Effective Date Rule" set on company level is not getting considered while allocating core plan(s) to "Rehired" employees

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: BenAdmin
    • Labels:
      None
    • Environment:
      Production
    • Bug Type:
      Functional
    • Bug Severity:
      Medium
    • Module:
      BenAdmin - Enrollment
    • Reported by:
      Harbinger
    • Item State:
      Production Complete - Closed
    • Issue Importance:
      Must Have
    • Sprint:
      WT Sprint 31-Bugs

      Description

      Customization :

      • Company Level Rehire Effective Date Rule : Date 1st of the Month following XX (1) Month from Date of Rehire
      • Company Level Effective Date Rule : Date of Change
      • No new-hire / re-hire effective date rule on plan level

      Steps to reproduce an issue :

      1. Add employee
      2. Core plans will be allocated as per new hire rules
      3. Change Employee's status to 'Terminated' from 'Change Status screen'
      4. Change Employee's status to 'Rehired' from 'Change Status screen'
      5. Core plans will not be allocated as per Rehire Effective Date Rule. Which is incorrect.

      Expected result :
      Core plans must be allocated as per eligible Rehire Effective Date Rule.

      Example :

      • If terminated employee's status is changed to Rehired with 06/23/2017 effective date.
      • System will not consider Rehire Effective Date Rule and will allocate core plan(s) as per Company Level Effective Date Rule.
      • Hence employee will get elections with 06/23/2017 effective date.

        Attachments

        1. Checklist_for_WT_9927.doc
          26 kB
        2. image001.jpg
          image001.jpg
          0.3 kB
        3. image001.jpg
          image001.jpg
          0.3 kB
        4. image002.png
          image002.png
          0.6 kB
        5. image002.png
          image002.png
          0.6 kB
        6. WT_9927_Affected_Files.txt
          0.1 kB

          Issue Links

            Activity

            abhilash.warkari Abhilash Warkari (Inactive) created issue -
            abhilash.warkari Abhilash Warkari (Inactive) made changes -
            Field Original Value New Value
            Assignee Vijay Siddha [ vijays ] Jyoti Mayne [ jyoti.mayne ]
            abhilash.warkari Abhilash Warkari (Inactive) made changes -
            Status Open [ 1 ] In Development [ 10007 ]
            abhilash.warkari Abhilash Warkari (Inactive) made changes -
            Summary *Rehire Effective Date Rule* set on company level is not getting considered while allocating core plan(s) to Rehired employees "Rehire Effective Date Rule" set on company level is not getting considered while allocating core plan(s) to "Rehired" employees
            jyoti.mayne Jyoti Mayne made changes -
            Link This issue relates to WT-9743 [ WT-9743 ]
            jyoti.mayne Jyoti Mayne made changes -
            Dev Due Date 29/Jun/2017
            umesh.kadam Umesh Kadam (Inactive) made changes -
            Description Customization :
            - Rehire Effective Date Rule : Date 1st of the Month following XX (1) Month from Date of Rehire
            - Company Level Effective Date Rule : Date of Change

            Steps to reproduce an issue :
            # Add employee
            # Core plans will be allocated as per new hire rules
            # Change Employee's status to 'Terminated' from 'Change Status screen'
            # Change Employee's status to 'Rehired' from 'Change Status screen'
            # Core plans will not be allocated as per Rehire Effective Date Rule. Which is incorrect.

            Expcted result :
            Core plans must be allocated as per eligibled Rehire Effective Date Rule.

            Example :
            - If terminated employee's status is changed to Rehired with 06/23/2017 effective date.
            - System will not consider Rehire Effective Date Rule and will allocate core plan(s) as per *Company Level Effective Date Rule*.
            - Hence employee will get elections with 06/23/2017 effective date.
            Customization :
            - Company Level Rehire Effective Date Rule : Date 1st of the Month following XX (1) Month from Date of Rehire
            - Company Level Effective Date Rule : Date of Change
            - No new-hire / re-hire effective date rule on plan level

            Steps to reproduce an issue :
            # Add employee
            # Core plans will be allocated as per new hire rules
            # Change Employee's status to 'Terminated' from 'Change Status screen'
            # Change Employee's status to 'Rehired' from 'Change Status screen'
            # Core plans will not be allocated as per Rehire Effective Date Rule. Which is incorrect.

            Expected result :
            Core plans must be allocated as per eligible Rehire Effective Date Rule.

            Example :
            - If terminated employee's status is changed to Rehired with 06/23/2017 effective date.
            - System will not consider Rehire Effective Date Rule and will allocate core plan(s) as per *Company Level Effective Date Rule*.
            - Hence employee will get elections with 06/23/2017 effective date.
            shailendra.honrao Shailendra Honrao (Inactive) made changes -
            Assignee Jyoti Mayne [ jyoti.mayne ] Shailendra Honrao [ shailendra.honrao ]
            umesh.kadam Umesh Kadam (Inactive) made changes -
            Remaining Estimate 0h [ 0 ]
            Time Spent 0.5h [ 1800 ]
            Worklog Id 58746 [ 58746 ]
            shailendra.honrao Shailendra Honrao (Inactive) made changes -
            Time Spent 0.5h [ 1800 ] 5.5h [ 19800 ]
            Worklog Id 58828 [ 58828 ]
            shailendra.honrao Shailendra Honrao (Inactive) made changes -
            Item State Parent values: Development(10200)Level 1 values: In Analysis(10204) Parent values: Development(10200)Level 1 values: Ready for Review(10208)
            shailendra.honrao Shailendra Honrao (Inactive) made changes -
            Item State Parent values: Development(10200)Level 1 values: Ready for Review(10208) Parent values: Development(10200)Level 1 values: Ready for Local Testing(10209)
            shailendra.honrao Shailendra Honrao (Inactive) made changes -
            Code Review Date 29/Jun/2017
            Code Reviewed By Jyoti Mayne [ 11910 ]
            Original Estimate 0h [ 0 ]
            shailendra.honrao Shailendra Honrao (Inactive) made changes -
            Attachment WT_9927_Affected_Files.txt [ 53722 ]
            shailendra.honrao Shailendra Honrao (Inactive) made changes -
            Attachment Checklist_for_WT_9927.doc [ 53723 ]
            jyoti.mayne Jyoti Mayne made changes -
            Assignee Shailendra Honrao [ shailendra.honrao ] Prasad Pise [ prasadp ]
            jyoti.mayne Jyoti Mayne made changes -
            Developer Shailendra Honrao [ shailendra.honrao ]
            prasadp Prasad Pise (Inactive) made changes -
            Assignee Prasad Pise [ prasadp ] Alankar Chavan [ alankar.chavan ]
            umesh.kadam Umesh Kadam (Inactive) made changes -
            Time Spent 5.5h [ 19800 ] 6.5h [ 23400 ]
            Worklog Id 59279 [ 59279 ]
            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)
            alankar.chavan Alankar Chavan (Inactive) made changes -
            Status In Development [ 10007 ] Local Testing [ 10200 ]
            alankar.chavan Alankar Chavan (Inactive) made changes -
            Item State Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) Parent values: LB QA(10201)Level 1 values: In Testing(10210)
            alankar.chavan Alankar Chavan (Inactive) made changes -
            Time Spent 6.5h [ 23400 ] 7.5h [ 27000 ]
            Worklog Id 59406 [ 59406 ]
            alankar.chavan Alankar Chavan (Inactive) made changes -
            Item State Parent values: LB QA(10201)Level 1 values: In Testing(10210) Parent values: LB QA(10201)Level 1 values: Ready for Stage(10213)
            shailendra.honrao Shailendra Honrao (Inactive) made changes -
            Time Spent 7.5h [ 27000 ] 13.5h [ 48600 ]
            Worklog Id 59418 [ 59418 ]
            shailendra.honrao Shailendra Honrao (Inactive) made changes -
            Code Reviewed By Jyoti Mayne [ 11910 ] Jyoti Mayne,Umesh Kadam [ 11910, 15302 ]
            jyoti.mayne Jyoti Mayne made changes -
            Time Spent 13.5h [ 48600 ] 14h [ 50400 ]
            Worklog Id 59530 [ 59530 ]
            alankar.chavan Alankar Chavan (Inactive) made changes -
            Production Due Date 04/Jul/2017
            Stage Due Date 3/Jul/17 [ 2017-07-03 ]
            ashwin.wankhede Ashwin Wankhede (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: LB Deployed(11600)
            jyoti.mayne Jyoti Mayne 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)
            khandu.kshirsagar Khandu Kshirsagar (Inactive) made changes -
            Item State Parent values: LB QA(10201)Level 1 values: Ready for Stage(10213) Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602)
            alankar.chavan Alankar Chavan (Inactive) made changes -
            Item State Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602) Parent values: Stage QA(10202)Level 1 values: Ready for Production(10217)
            alankar.chavan Alankar Chavan (Inactive) made changes -
            Status Local Testing [ 10200 ] Stage Testing [ 10201 ]
            shailendra.honrao Shailendra Honrao (Inactive) made changes -
            Attachment image001.jpg [ 53931 ]
            Attachment image002.png [ 53932 ]
            shailendra.honrao Shailendra Honrao (Inactive) made changes -
            Attachment image001.jpg [ 53933 ]
            Attachment image002.png [ 53934 ]
            khandu.kshirsagar Khandu Kshirsagar (Inactive) made changes -
            Item State Parent values: Stage QA(10202)Level 1 values: Ready for Production(10217) Parent values: Production QA(10203)Level 1 values: Production Deployed(10221)
            alankar.chavan Alankar Chavan (Inactive) made changes -
            Status Stage Testing [ 10201 ] Production Testing [ 10202 ]
            alankar.chavan Alankar Chavan (Inactive) made changes -
            Resolution Fixed [ 1 ]
            Status Production Testing [ 10202 ] Production Complete [ 10028 ]
            alankar.chavan Alankar Chavan (Inactive) made changes -
            Status Production Complete [ 10028 ] Closed [ 6 ]
            alankar.chavan Alankar Chavan (Inactive) made changes -
            Item State Parent values: Production QA(10203)Level 1 values: Production Deployed(10221) Parent values: Production Complete(10222)Level 1 values: Closed(10223)
            alankar.chavan Alankar Chavan (Inactive) made changes -
            Time Spent 14h [ 50400 ] 17h [ 61200 ]
            Worklog Id 60527 [ 60527 ]
            rakeshr Rakesh Roy (Inactive) made changes -
            Bug Severity Medium [ 16702 ]
            satyap Satya made changes -
            Environment_New Production [ 18442 ]

              People

              Assignee:
              alankar.chavan Alankar Chavan (Inactive)
              Reporter:
              abhilash.warkari Abhilash Warkari (Inactive)
              Developer:
              Shailendra Honrao (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Dev Due Date:
                Pre-Prod Due Date:
                Production Due Date:
                Code Review Date:

                  Time Tracking

                  Estimated:
                  Original Estimate - 0h
                  0h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 17h
                  17h