Project SimpleProject Type: software

Project Simple

Uploaded image for project: 'Project Simple'
  1. Project Simple
  2. ST-389

LB | Partner | Benefit Cloning | Cloning icons (both ) New Benefit Type Name text field throwing server error

    Details

    • Environment:
      QA
    • Bug Type:
      Functional
    • Bug Severity:
      Medium
    • Level:
      Partner
    • Module:
      BenAdmin - Enrollment
    • Reported by:
      Harbinger
    • Company:
      All Clients/Multiple Clients
    • Item State:
      LB QA - On Hold
    • Sprint:
      WT Sprint 39 - Bugs

      Description

      Environment: LB
      Company: FDU for Hspl
      Login: Partner

      Issue: text field "New Benefit Type Name" throwing server when text count goes beyond 50 characters.

      Screen capture and error log for the same is attached with jira.
      Hrishikesh Deshpande

        Attachments

        1. ST_389_Affected_Files.txt
          0.2 kB
        2. newTextNAme.txt
          0.3 kB
        3. NewNameError.jpg
          NewNameError.jpg
          172 kB
        4. Checklist_for_ST_389.doc
          26 kB

          Issue Links

          relates to

          Enhancement - An improvement or enhancement to an existing feature or task. ST-345 Benefit Type Clonning

          • Medium - Has the potential to affect progress.
          • In Development

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            shailendra.honrao Shailendra Honrao (Inactive) added a comment -

            Hi Priya Dhamande,
            Please find below 3 C's

            Cause If New Benefit Type Name exceeds beyond 50 characters then server error has occurred.
            Concern In BenefitType table definition, Benefit type name column has allowed to store up-to 50 characters only.
            Correction We have added maxlength validation on UI.

            Thanks,
            Shailendra Honrao

            Cc:Jyoti Mayne,Umesh Kadam,Snehal Shabade

            Show
            shailendra.honrao Shailendra Honrao (Inactive) added a comment - Hi Priya Dhamande , Please find below 3 C's Cause If New Benefit Type Name exceeds beyond 50 characters then server error has occurred. Concern In BenefitType table definition, Benefit type name column has allowed to store up-to 50 characters only. Correction We have added maxlength validation on UI. Thanks, Shailendra Honrao Cc: Jyoti Mayne , Umesh Kadam , Snehal Shabade
            Hide
            Permalink
            priya.dhamande Priya Dhamande (Inactive) added a comment -

            Hi,

            Keeping this jira on Hold, till related enhancement (NF-345) and its bug (NF-390 and NF-391) are deployed on LB.

            Hrishikesh Deshpande Rakesh Roy Shailendra Honrao Snehal Shabade Jyoti Mayne Umesh Kadam

            Show
            priya.dhamande Priya Dhamande (Inactive) added a comment - Hi, Keeping this jira on Hold, till related enhancement ( NF-345 ) and its bug ( NF-390 and NF-391 ) are deployed on LB. Hrishikesh Deshpande Rakesh Roy Shailendra Honrao Snehal Shabade Jyoti Mayne Umesh Kadam
            Hide
            Permalink
            priya.dhamande Priya Dhamande (Inactive) added a comment -

            Environment: LB
            Company: FDU for Hspl
            Login: Partner

            The issue of server error is implemented and verified on LB and its working as expected.

            On Benefit Type page and First page of Benefit type on both pages and for both Clone and Clone To company page, no server error found and validation is displayed.

            This jira is kept on Hold, till ST-397 (bug related to enhancement) is deployed and verified on LB.

            Hrishikesh Deshpande Rakesh Roy

            Show
            priya.dhamande Priya Dhamande (Inactive) added a comment - Environment: LB Company: FDU for Hspl Login: Partner The issue of server error is implemented and verified on LB and its working as expected. On Benefit Type page and First page of Benefit type on both pages and for both Clone and Clone To company page, no server error found and validation is displayed. This jira is kept on Hold, till ST-397 (bug related to enhancement) is deployed and verified on LB. Hrishikesh Deshpande Rakesh Roy

              People

              Assignee:
              priya.dhamande Priya Dhamande (Inactive)
              Reporter:
              priya.dhamande Priya Dhamande (Inactive)
              Developer:
              Shailendra Honrao (Inactive)
              QA:
              Priya Dhamande (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

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

                  Time Tracking

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