Uploaded image for project: 'New Features 2017'
  1. New Features 2017
  2. NF-686

TSR Integration->Tour Eligibility->Employee is getting same tour twice when different tours are mapped with different job id.

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Integrations
    • Labels:
      None
    • Module:
      TSR
    • Reported by:
      Harbinger
    • Item State:
      Production Complete - Closed
    • Issue Importance:
      Q1

      Description

      1. Launch the Postman app.
      2. Select “Post” request from dropdown.
      3. Select authorization type as “Basic Auth”.
      4. Enter valid User ID and Password.
      5. Enter below URL:
      https://10.0.2.120/api/employee/addEmployeeTour
      6. Pass the require parameter using body. (Job ID =J1 and Tour ID =30)
      7. Click on Send button.
      8. Now change Job ID=J2 and Tour ID=32.
      9. Click on Send button.
      10. Two different tours get assigned to employee with different Job ID.
      11. Traverse the tour using employee login.

      Actual Result:
      After completing first tour employee again get same tour, then after completing it for second time he gets other tour.
      Expected Result:
      Employee should get each tour only once.

      Cc: Saurabh Sablaka, Prasad Pise

        Attachments

          Issue Links

            Activity

            Hide
            ramya.tantry Ramya Tantry (Inactive) added a comment -

            Hi Kunal Kedari,

            Please verify this Issue.
            Concern: Employee is getting same tour twice when different tours are mapped with different job id.
            Cause:One condition for checking eligible tour ids are empty was missing.Due to this 2 tours were getting assigned.
            Correction: Condition is added to verify where tour id's are empty or not.

            Show
            ramya.tantry Ramya Tantry (Inactive) added a comment - Hi Kunal Kedari , Please verify this Issue. Concern : Employee is getting same tour twice when different tours are mapped with different job id. Cause :One condition for checking eligible tour ids are empty was missing.Due to this 2 tours were getting assigned. Correction : Condition is added to verify where tour id's are empty or not.
            Hide
            kunal.kedari Kunal Kedari (Inactive) added a comment -

            If there are two tours in application (OB1 tourid=12 and OB2 tourid=13) to which employee added through API is eligible, then in this scenario if we pass tourid=12 through api then both tours (OB1 and OB2) get assigned to employee.

            Please refer below screenshot for more details. Reopening the issue.

            Cc: Saurabh Sablaka, Prasad Pise

            Show
            kunal.kedari Kunal Kedari (Inactive) added a comment - If there are two tours in application (OB1 tourid=12 and OB2 tourid=13) to which employee added through API is eligible, then in this scenario if we pass tourid=12 through api then both tours (OB1 and OB2) get assigned to employee. Please refer below screenshot for more details. Reopening the issue. Cc: Saurabh Sablaka , Prasad Pise
            Hide
            ramya.tantry Ramya Tantry (Inactive) added a comment -

            Hi Kunal Kedari,

            Please verify the mentioned scenario.

            Show
            ramya.tantry Ramya Tantry (Inactive) added a comment - Hi Kunal Kedari , Please verify the mentioned scenario.
            Hide
            kunal.kedari Kunal Kedari (Inactive) added a comment -

            Verified the fix on Stage environment, now employee is not getting same tour twice. Marking status as "Production Deployment on Hold"

            Show
            kunal.kedari Kunal Kedari (Inactive) added a comment - Verified the fix on Stage environment, now employee is not getting same tour twice. Marking status as "Production Deployment on Hold"

              People

              Assignee:
              kunal.kedari Kunal Kedari (Inactive)
              Reporter:
              kunal.kedari Kunal Kedari (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 8h
                  8h
                  Remaining:
                  Time Spent - 6h Remaining Estimate - 2h
                  2h
                  Logged:
                  Time Spent - 6h Remaining Estimate - 2h
                  6h