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

NH effective date rules on plan design is overriding the additional eligibility

    Details

    • Type: Enhancement
    • Status: In Development
    • Priority: Medium
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: BenAdmin
    • Environment:
      Stage
    • Module:
      BenAdmin - EDS
    • Reported by:
      Implementation
    • Company:
      All Clients/Multiple Clients
    • Item State:
      Development - In Analysis
    • Sprint:
      WT Sprint 41
    • Severity:
      Simple

      Description

      When the New Hire rule is setup on the plan design, in the Eligibility tab, to be effective 6 months from DOH this rules overrides the Additional Eligibility rule (AND IS new hire = to NO) this means when the new hire rule is setup on the plan the NH ends up seeing the plan in the NH enrollment tunnel. They should not be able to see the plan if they are a NH.

      Speaking with Amit Thorve it was advised that the "The eligibility should always take a precedence. If eligibility fails then plans should not be available for employee."

      Please review and provide feedback on when this bug can be corrected.

      CC:Gary Cunninghampeggy fiedlerRobyn AdkisonYamilka CocaAmit Thorve

        Attachments

          Issue Links

            Activity

            Hide
            rohit.shete Rohit Shete (Inactive) added a comment -

            Hi Swapnil Pandhare,

            As discussed, the issue reported in WT-12271 occurred due to code fix for WT-10797.

            Please look into this.

            Thanks and Regard,
            Rohit Shete

            CC : Samir, Satya, Amruta Lohiya, Jyoti Mayne, Umesh Kadam

            Show
            rohit.shete Rohit Shete (Inactive) added a comment - Hi Swapnil Pandhare , As discussed, the issue reported in WT-12271 occurred due to code fix for WT-10797 . Please look into this. Thanks and Regard, Rohit Shete CC : Samir , Satya , Amruta Lohiya , Jyoti Mayne , Umesh Kadam
            Hide
            niteen.surwase Niteen Surwase (Inactive) added a comment -

            Hi Rohit Shete

            We have made changes in SP. I've executed it on Rohit_Stage_BioRad. Please verify it and let us know whether it is working or not. SP sent you through email.

            Thanks,
            Niteen S.

            Cc: Swapnil Pandhare Amruta Lohiya

            Show
            niteen.surwase Niteen Surwase (Inactive) added a comment - Hi Rohit Shete We have made changes in SP. I've executed it on Rohit_Stage_BioRad. Please verify it and let us know whether it is working or not. SP sent you through email. Thanks, Niteen S. Cc: Swapnil Pandhare Amruta Lohiya
            Hide
            rohit.shete Rohit Shete (Inactive) added a comment -

            Hi Niteen Surwase,

            We have tested related scenarios for this issue and those are working well. Please verify at your end and update.

            Thanks and Regard,
            Rohit Shete

            CC : Satya, Amruta Lohiya, Swapnil Pandhare, Jyoti Mayne, Umesh Kadam

            Show
            rohit.shete Rohit Shete (Inactive) added a comment - Hi Niteen Surwase , We have tested related scenarios for this issue and those are working well. Please verify at your end and update. Thanks and Regard, Rohit Shete CC : Satya , Amruta Lohiya , Swapnil Pandhare , Jyoti Mayne , Umesh Kadam
            Hide
            niteen.surwase Niteen Surwase (Inactive) added a comment -

            Hi Swapnil Pandhare

            Changes has been done (Reverted from NF-2698) and tested on trunk. It is working as earlier was.
            Changes are ready for LB.

            Thanks,
            Cc; Satya Sheetal Bodhale Rohit Shete Gaurav Sodani

            Show
            niteen.surwase Niteen Surwase (Inactive) added a comment - Hi Swapnil Pandhare Changes has been done (Reverted from NF-2698 ) and tested on trunk. It is working as earlier was. Changes are ready for LB. Thanks, Cc; Satya Sheetal Bodhale Rohit Shete Gaurav Sodani
            Hide
            gaurav.sodani Gaurav Sodani (Inactive) added a comment -

            Hi All,

            Keeping the ticket on hold, as it has not been approved for stage deployment

            Regards
            Gaurav

            Show
            gaurav.sodani Gaurav Sodani (Inactive) added a comment - Hi All, Keeping the ticket on hold, as it has not been approved for stage deployment Regards Gaurav
            Hide
            rakeshr Rakesh Roy (Inactive) added a comment - - edited

            Niteen Surwase As discussed with you, this is ready for local testing.Not deployed on LB.
            Gaurav SodaniSwapnil Pandhare

            Show
            rakeshr Rakesh Roy (Inactive) added a comment - - edited Niteen Surwase As discussed with you, this is ready for local testing.Not deployed on LB. Gaurav Sodani Swapnil Pandhare
            Hide
            amjohnson Amannda Johnson added a comment -

            Please provide ETA on when this will be ready to test in stage and production.

            Show
            amjohnson Amannda Johnson added a comment - Please provide ETA on when this will be ready to test in stage and production.
            Hide
            niteen.surwase Niteen Surwase (Inactive) added a comment -

            Hi Amannda Johnson

            It will be taken in Sprint 41 and it is planned on Stage by 23rd Dec.

            Thanks,
            Niteen S.

            Cc: Swapnil Pandhare Gaurav Sodani Satya

            Show
            niteen.surwase Niteen Surwase (Inactive) added a comment - Hi Amannda Johnson It will be taken in Sprint 41 and it is planned on Stage by 23rd Dec . Thanks, Niteen S. Cc: Swapnil Pandhare Gaurav Sodani Satya
            Hide
            gaurav.sodani Gaurav Sodani (Inactive) added a comment -

            Hi All,

            Attaching the development approval email for your reference

            Regards
            Gaurav

            Show
            gaurav.sodani Gaurav Sodani (Inactive) added a comment - Hi All, Attaching the development approval email for your reference Regards Gaurav
            Hide
            Yamilka.Coca Yamilka Coca (Inactive) added a comment -

            Hello - Does this item still need to be deployed to prod, after the 12/23 deployment to stage? Thank you.

            Show
            Yamilka.Coca Yamilka Coca (Inactive) added a comment - Hello - Does this item still need to be deployed to prod, after the 12/23 deployment to stage? Thank you.
            Hide
            niteen.surwase Niteen Surwase (Inactive) added a comment - - edited

            Hi Swapnil Pandhare

            As this change is Ready for LB.
            I've done with unit testing for this change to make sure that it is working as earlier.
            Is New Hire macro is worked fine on Plan Design at below levels:

            • SA/P/B Login at EE level - Done
            • Company Admin Login at EE level - Done
            • EE Login - Done

            Thanks,
            Niteen S.

            Cc: Swapnil Pandhare Satya Gaurav Sodani

            Show
            niteen.surwase Niteen Surwase (Inactive) added a comment - - edited Hi Swapnil Pandhare As this change is Ready for LB. I've done with unit testing for this change to make sure that it is working as earlier. Is New Hire macro is worked fine on Plan Design at below levels: SA/P/B Login at EE level - Done Company Admin Login at EE level - Done EE Login - Done Thanks, Niteen S. Cc: Swapnil Pandhare Satya Gaurav Sodani
            Hide
            niteen.surwase Niteen Surwase (Inactive) added a comment -

            [~meghana joshi], This has been deployed on LB.

            Show
            niteen.surwase Niteen Surwase (Inactive) added a comment - [~meghana joshi] , This has been deployed on LB.
            Hide
            priya.dhamande Priya Dhamande (Inactive) added a comment -

            Environment: LB
            Company: For QA FDU for hspl
            Login: Partner, Employee and Company Admin

            The bug is tested for attached test scenarios. Status for the test cases is atatched with jira.

            All the cases worked as expected for mentioned logins. So, moving this jira on Stage.

            Hrishikesh Deshpande Sachin Hingole

            Show
            priya.dhamande Priya Dhamande (Inactive) added a comment - Environment: LB Company: For QA FDU for hspl Login: Partner, Employee and Company Admin The bug is tested for attached test scenarios. Status for the test cases is atatched with jira. All the cases worked as expected for mentioned logins. So, moving this jira on Stage. Hrishikesh Deshpande Sachin Hingole
            Hide
            gaurav.sodani Gaurav Sodani (Inactive) added a comment -

            Hi All,

            This ticket has been approved for stage deployment on 12/21/17.

            Regards
            Gaurav

            Show
            gaurav.sodani Gaurav Sodani (Inactive) added a comment - Hi All, This ticket has been approved for stage deployment on 12/21/17. Regards Gaurav
            Hide
            priya.dhamande Priya Dhamande (Inactive) added a comment -

            Environment: Stage
            Company: FDU for hspl
            Login: Partner, Employee and Company Admin

            The enhancement is tested for attached scenarios. All scenarios worked as expected. Status for the same is updated and attached with jira.

            As scenarios worked as expected, moving jira on Production.

            Hrishikesh Deshpande Sachin Hingole

            Show
            priya.dhamande Priya Dhamande (Inactive) added a comment - Environment: Stage Company: FDU for hspl Login: Partner, Employee and Company Admin The enhancement is tested for attached scenarios. All scenarios worked as expected. Status for the same is updated and attached with jira. As scenarios worked as expected, moving jira on Production. Hrishikesh Deshpande Sachin Hingole
            Hide
            amjohnson Amannda Johnson added a comment -

            When will this be released onto stage? I just tested, on BioRad stage site, and my first test failed. I added a new hire and e-trade benefit type showed in the New Hire enrollment tunnel. Since they are a New Hire they should not see the e-trade plans at all. The new hire I added is employee "EsppNH Test" with a date of hire of 12/10/2017.

            Show
            amjohnson Amannda Johnson added a comment - When will this be released onto stage? I just tested, on BioRad stage site, and my first test failed. I added a new hire and e-trade benefit type showed in the New Hire enrollment tunnel. Since they are a New Hire they should not see the e-trade plans at all. The new hire I added is employee "EsppNH Test" with a date of hire of 12/10/2017.
            Hide
            priya.dhamande Priya Dhamande (Inactive) added a comment -

            Amannda Johnson,

            The test cases are covered without considering the New Hire Effective Date Rule.
            We need to fix this issue considering the New Hire Effective Date Rule. So, reopening the jira for the same.

            Niteen Surwase Satya Hrishikesh Deshpande

            Show
            priya.dhamande Priya Dhamande (Inactive) added a comment - Amannda Johnson , The test cases are covered without considering the New Hire Effective Date Rule. We need to fix this issue considering the New Hire Effective Date Rule. So, reopening the jira for the same. Niteen Surwase Satya Hrishikesh Deshpande
            Hide
            niteen.surwase Niteen Surwase (Inactive) added a comment - - edited

            Hi Amannda Johnson

            Please find below detailed analysis of different scenarios and system behavior:

            Scenario I:

            1. Additional Criteria on Plan Eligibility : Is New Hire = No AND
            2. NH Effective Date rules with Waiting Period of 6 Months from Date of Hire

            Then plan Effective date will be calculated considering 6 months waiting period.
            As per system behavior, Then that Effective Date will be considered for additional criteria (i.e in our case Is New Hire).
            For that effective date if employee is not New Hire then, it satisfies above 1st criteria and shows plan for employee.

            Current Example-

            Plan Customization on company BioRad :
            1. Additional Criteria on Plan Eligibility : Is New Hire = No AND
            2. NH Effective Date rules with Waiting Period 6 Months from Date of Hire.

            Employee Hire Date of mentioned Employee (EsppNH Test) : 12/10/2017

            Plan's Effective Date will be 6 Months from Date of Hire = 06/10/2018
            Then system will check Is New Hire criteria at the Effective Date of 06/10/2018 AND for this effective date, employee is not New Hire.
            So, It is satisfying 1st criteria and plan will be visible to employee.

            Scenario II:

            Only Additional Criteria on Plan Eligibility : Is New Hire = No
            AND NH Effective Date rules not set.
            Then, plan will be visible accordingly to Employee New hire.

            Example-
            1. Additional Criteria on Plan Eligibility : Is New Hire = No
            Employee Hire Date : 12/20/2017

            Plan's Effective Date = 12/20/2017
            As per system behavior, At the Effective Date of 12/20/2017 employee will be New Hire.
            So, as per 1st criteria in plan customization, plan will not be visible to employee.

            Note: As per system behavior, first priority is always given to plan Dating Eligibility Rule.

            Observation:

            If we are setting additional criteria as Is New Hire = No AND also setting NH Effective Date rules with Waiting Period on plan design, then both the conditions are contradicting to each other by checking New Hire and adding Waiting Period to NH Effective Date.

            If we don't want to show plan in New Hire, use either additional criteria as Is New Hire = No OR NH Effective Date rules with Waiting Period on plan design.
            1. If we set criteria Is New Hire = No, then It'll not show plan in New Hire mode, it'll only visible after New Hire.
            OR
            2. If we set NH Effective Date rules with Waiting Period, then It'll show plan exactly after waiting period time.

            QA Comments:
            We have tried to achieve result with below customization on Hspl copy.

            1. Created Split Plans for New Hire and Existing Employee
            2. Created two Eligibility rules for existing and new Hire employees
            3. For New Hire Employee Plan customization:

            Additional criteria:
            Is New Hire Yes
            And Employer. Two Year Indicator not equal to Y

            Dating Eligibility Rule:
            New Hire Effective Date Rule
            Use Waiting period > XX months from Date of Hire > 6
            Now with this customization, New Hire Employee will not get the Plan in tunnel.

            4. For Existing Employee Plan
            Additional criteria:
            Is New Hire No
            And with this customization, existing employee will get plan as per mode available.

            Thanks,
            Niteen S.

            CC: Swapnil Pandhare Satya Gaurav Sodani Sheetal Bodhale Umesh Kadam Priya Dhamande

            Show
            niteen.surwase Niteen Surwase (Inactive) added a comment - - edited Hi Amannda Johnson Please find below detailed analysis of different scenarios and system behavior: Scenario I: 1. Additional Criteria on Plan Eligibility : Is New Hire = No AND 2. NH Effective Date rules with Waiting Period of 6 Months from Date of Hire Then plan Effective date will be calculated considering 6 months waiting period. As per system behavior, Then that Effective Date will be considered for additional criteria (i.e in our case Is New Hire). For that effective date if employee is not New Hire then, it satisfies above 1st criteria and shows plan for employee. Current Example- Plan Customization on company BioRad : 1. Additional Criteria on Plan Eligibility : Is New Hire = No AND 2. NH Effective Date rules with Waiting Period 6 Months from Date of Hire. Employee Hire Date of mentioned Employee (EsppNH Test) : 12/10/2017 Plan's Effective Date will be 6 Months from Date of Hire = 06/10/2018 Then system will check Is New Hire criteria at the Effective Date of 06/10/2018 AND for this effective date, employee is not New Hire. So, It is satisfying 1st criteria and plan will be visible to employee. Scenario II: Only Additional Criteria on Plan Eligibility : Is New Hire = No AND NH Effective Date rules not set . Then, plan will be visible accordingly to Employee New hire. Example- 1. Additional Criteria on Plan Eligibility : Is New Hire = No Employee Hire Date : 12/20/2017 Plan's Effective Date = 12/20/2017 As per system behavior, At the Effective Date of 12/20/2017 employee will be New Hire . So, as per 1st criteria in plan customization, plan will not be visible to employee. Note: As per system behavior, first priority is always given to plan Dating Eligibility Rule. Observation: If we are setting additional criteria as Is New Hire = No AND also setting NH Effective Date rules with Waiting Period on plan design, then both the conditions are contradicting to each other by checking New Hire and adding Waiting Period to NH Effective Date. If we don't want to show plan in New Hire, use either additional criteria as Is New Hire = No OR NH Effective Date rules with Waiting Period on plan design. 1. If we set criteria Is New Hire = No , then It'll not show plan in New Hire mode , it'll only visible after New Hire. OR 2. If we set NH Effective Date rules with Waiting Period , then It'll show plan exactly after waiting period time . QA Comments: We have tried to achieve result with below customization on Hspl copy. 1. Created Split Plans for New Hire and Existing Employee 2. Created two Eligibility rules for existing and new Hire employees 3. For New Hire Employee Plan customization: Additional criteria : Is New Hire Yes And Employer. Two Year Indicator not equal to Y Dating Eligibility Rule : New Hire Effective Date Rule Use Waiting period > XX months from Date of Hire > 6 Now with this customization, New Hire Employee will not get the Plan in tunnel. 4. For Existing Employee Plan Additional criteria : Is New Hire No And with this customization, existing employee will get plan as per mode available. Thanks, Niteen S. CC: Swapnil Pandhare Satya Gaurav Sodani Sheetal Bodhale Umesh Kadam Priya Dhamande
            Hide
            priya.dhamande Priya Dhamande (Inactive) added a comment -

            Amannda Johnson,

            We can have call on Tuesday if more inputs required from our end.

            Satya Gaurav Sodani Sheetal Bodhale Umesh Kadam Niteen Surwase Hrishikesh Deshpande

            Show
            priya.dhamande Priya Dhamande (Inactive) added a comment - Amannda Johnson , We can have call on Tuesday if more inputs required from our end. Satya Gaurav Sodani Sheetal Bodhale Umesh Kadam Niteen Surwase Hrishikesh Deshpande
            Hide
            amjohnson Amannda Johnson added a comment -

            Niteen Surwase
            Based on a conversation with Amit Thorve, back on 11/21/17, if the additional eligibility has Is New Hire = No AND the New Hire effective date rules are set the New Hire Effective date rule should not over the additional eligibility rule. We have both rules set this way after the 31 day window closes for the New Hire the earliest effective date that they can get, should they use the ESPP QE, would be 6 months from Date of Hire.

            You mention "If we don't want to show plan in New Hire, use either additional criteria as Is New Hire = No OR NH Effective Date rules with Waiting Period on plan design." However I removed the Is New Hire = No from the additional eligibility and left the NH Effective Date rules on the plan design and the plan still shows in the employees new hire enrollment tunnel.

            The purpose of use both the and Is New Hire = No + the 6months from DOH NH effective date rule is to help make sure the plan doesn't show up in the new hire enrollment and to make sure that when the new hire enrollment window is over (31 days from doh) the earliest effective the employee could get on the ESPP plan is 6months from the date of hire.

            Priya Dhamande
            For Tuesday, regarding a call, Yes if there are still questions on what is needed lets have a call on Tuesday. Please let me know what time is best this way I can help make myself available to discuss.

            Show
            amjohnson Amannda Johnson added a comment - Niteen Surwase Based on a conversation with Amit Thorve , back on 11/21/17, if the additional eligibility has Is New Hire = No AND the New Hire effective date rules are set the New Hire Effective date rule should not over the additional eligibility rule. We have both rules set this way after the 31 day window closes for the New Hire the earliest effective date that they can get, should they use the ESPP QE, would be 6 months from Date of Hire. You mention "If we don't want to show plan in New Hire, use either additional criteria as Is New Hire = No OR NH Effective Date rules with Waiting Period on plan design." However I removed the Is New Hire = No from the additional eligibility and left the NH Effective Date rules on the plan design and the plan still shows in the employees new hire enrollment tunnel. The purpose of use both the and Is New Hire = No + the 6months from DOH NH effective date rule is to help make sure the plan doesn't show up in the new hire enrollment and to make sure that when the new hire enrollment window is over (31 days from doh) the earliest effective the employee could get on the ESPP plan is 6months from the date of hire. Priya Dhamande For Tuesday, regarding a call, Yes if there are still questions on what is needed lets have a call on Tuesday. Please let me know what time is best this way I can help make myself available to discuss.
            Hide
            gaurav.sodani Gaurav Sodani (Inactive) added a comment -

            Hi All,

            Attaching the production deployment approval email for reference

            Regards
            Gaurav

            Show
            gaurav.sodani Gaurav Sodani (Inactive) added a comment - Hi All, Attaching the production deployment approval email for reference Regards Gaurav
            Hide
            amitthorve Amit Thorve (Inactive) added a comment -

            What is the resolution for this? As per my understanding the eligibility rules should always kick in first and then the effective date rules. If employee is not eligible for the plan then why the plan should show up in the tunnel of new hire?

            Show
            amitthorve Amit Thorve (Inactive) added a comment - What is the resolution for this? As per my understanding the eligibility rules should always kick in first and then the effective date rules. If employee is not eligible for the plan then why the plan should show up in the tunnel of new hire?
            Hide
            niteen.surwase Niteen Surwase (Inactive) added a comment -

            Hi Amannda Johnson

            This is the system behaviour. On plan level NH Effective Date rules with Waiting Period is set then eligibility of that plan will check as per rule effective date.
            Currently, we cant achieve the requirement by using NH Effective Date rule.
            So please remove NH Effective Date rule and keep the additional criteria as Is New Hire = No.
            To achieve mentioned requirement, we need enhancement. So we will create another ticket for workaround/enhancement after our call discussion.

            Note:
            As per discussion with Amit Thorve, employee will raise QE and then will do enrollment in this plan but effective date should be 6 months after new hire.
            So approach is, same like new hire we need to introduce QE rule on plan level. We are doing more analysis on this.

            Meanwhile, we are thinking on short term workaround and will get back to you.

            Thanks,
            Niteen S.

            Cc: Swapnil Pandhare Satya Gaurav Sodani Amruta Lohiya Umesh Kadam Jyoti Mayne Priya Dhamande

            Show
            niteen.surwase Niteen Surwase (Inactive) added a comment - Hi Amannda Johnson This is the system behaviour. On plan level NH Effective Date rules with Waiting Period is set then eligibility of that plan will check as per rule effective date. Currently, we cant achieve the requirement by using NH Effective Date rule. So please remove NH Effective Date rule and keep the additional criteria as Is New Hire = No . To achieve mentioned requirement, we need enhancement. So we will create another ticket for workaround/enhancement after our call discussion. Note: As per discussion with Amit Thorve , employee will raise QE and then will do enrollment in this plan but effective date should be 6 months after new hire. So approach is, same like new hire we need to introduce QE rule on plan level. We are doing more analysis on this. Meanwhile, we are thinking on short term workaround and will get back to you. Thanks, Niteen S. Cc: Swapnil Pandhare Satya Gaurav Sodani Amruta Lohiya Umesh Kadam Jyoti Mayne Priya Dhamande
            Hide
            priya.dhamande Priya Dhamande (Inactive) added a comment -

            MOM of yesterday's call

            Attendees: Amannda, Gaurav, Niteen and Priya
            Date: 03/01/2018
            Time: 9.30 to 10.05 PM IST

            Points:
            1. Explaining current System behavior
            2. Getting exact requirement from Amannda
            3. Action Point: Finding work around or Need to develop for the requirement

            Show
            priya.dhamande Priya Dhamande (Inactive) added a comment - MOM of yesterday's call Attendees: Amannda, Gaurav, Niteen and Priya Date: 03/01/2018 Time: 9.30 to 10.05 PM IST Points: 1. Explaining current System behavior 2. Getting exact requirement from Amannda 3. Action Point: Finding work around or Need to develop for the requirement
            Hide
            priya.dhamande Priya Dhamande (Inactive) added a comment -

            In order to remove the e-Trade plan from Employee tunnel with current system behavior below customization is required:

            On Plan:
            is New Hire is equal to No
            And remove New Hire Effective Date rule.

            Workaround:
            To make the Plan Effective after 6 months below customization to be done
            1. Create QE with with waiting period of 5 months
            Effective Date Rule > Use Waiting Period > 5 months from Event date
            2. Admin have to raise QE immediately after New Hire Period is completed otherwise the Effective Date may extend as per QE raised date.
            3. Now, Employee will be eligible for e-Trade Plan, effective after approx. 6 months.

            Note: Effective Date may extend, if QE not raise immediately after the New Hire window period completion. If Admin/Employee wants to enroll in Plan he should raise above created QE only.

            This is a manual and temporary work around.

            We will create new development jira for enhancement.

            Please check the same customization at your end and lets close the jira.

            Satya Gaurav Sodani Swapnil Eksambekar Umesh Kadam Amruta Lohiya Jyoti Agrawal Niteen Surwase Hrishikesh Deshpande

            Show
            priya.dhamande Priya Dhamande (Inactive) added a comment - In order to remove the e-Trade plan from Employee tunnel with current system behavior below customization is required: On Plan: is New Hire is equal to No And remove New Hire Effective Date rule. Workaround: To make the Plan Effective after 6 months below customization to be done 1. Create QE with with waiting period of 5 months Effective Date Rule > Use Waiting Period > 5 months from Event date 2. Admin have to raise QE immediately after New Hire Period is completed otherwise the Effective Date may extend as per QE raised date. 3. Now, Employee will be eligible for e-Trade Plan, effective after approx. 6 months. Note : Effective Date may extend, if QE not raise immediately after the New Hire window period completion. If Admin/Employee wants to enroll in Plan he should raise above created QE only. This is a manual and temporary work around. We will create new development jira for enhancement. Please check the same customization at your end and lets close the jira. Satya Gaurav Sodani Swapnil Eksambekar Umesh Kadam Amruta Lohiya Jyoti Agrawal Niteen Surwase Hrishikesh Deshpande
            Hide
            amjohnson Amannda Johnson added a comment -

            Jennifer Reed - Jackie Sivigny and I spoke today. Can we get this added to the list to get transitioned from a BUG to an enhancement?

            Show
            amjohnson Amannda Johnson added a comment - Jennifer Reed - Jackie Sivigny and I spoke today. Can we get this added to the list to get transitioned from a BUG to an enhancement?
            Hide
            Jennifer.Reed Jennifer Reed (Inactive) added a comment -

            Amannda Johnson Thanks Amannda, this has been moved to an enhancement. Satya Gaurav Sodani Can we touch base on this ticket?

            Show
            Jennifer.Reed Jennifer Reed (Inactive) added a comment - Amannda Johnson Thanks Amannda, this has been moved to an enhancement. Satya Gaurav Sodani Can we touch base on this ticket?
            Hide
            satyap Satya added a comment -

            Hi Jennifer Reed,

            As discussed in our call on 29th Jan 2018, Amannda Johnson was trying this through customization on BioRad-stage copy.

            Please let us know in case you hear updates on this?

            Regards,
            Satya Prakash

            Show
            satyap Satya added a comment - Hi Jennifer Reed , As discussed in our call on 29th Jan 2018, Amannda Johnson was trying this through customization on BioRad-stage copy. Please let us know in case you hear updates on this? Regards, Satya Prakash

              People

              Assignee:
              amjohnson Amannda Johnson
              Reporter:
              amjohnson Amannda Johnson
              QA:
              Hrishikesh Deshpande (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Dates

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

                  Time Tracking

                  Estimated:
                  Original Estimate - 15h Original Estimate - 15h
                  15h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 98h 44m
                  98h 44m