Zain KSA upgradation
  1. Zain KSA upgradation
  2. ZKU-232

Need To Implement Rule For Duplicate Node With Different Model_Huawei

      Details

      • Customer:
        Zain KSA 3.X

        Description

        Dear @Bassem Sabbagh,

        As per our earlier discussion, kindly assign an AI DEV resource to implement a rule for parsing nodes as outlined below:

        Note: This rule will apply when the same node (NEName) appears with two different models. The first model will be "BTS5900" and the second one will be "BTS3900" (see example for reference).

        Rule: We need to parse only the node that comes with NEType="BTS5900" and ignore the one with NEType="BTS3900".

        Example: For the node (NEName="ARR0519-P1-HUB_SRAN-FON"), it appears in the dump with two different models: NEType="BTS5900" and NEType="BTS3900". We need to parse only the entry with NEType="BTS5900" and disregard the entry with NEType="BTS3900".

        Best regards,
        Indrasan

        Issue Links

        blocks

        Task - A task that needs to be done. ZKU-94 Huawei RAN_Dumps , XML and NEP data Validation

        • Normal - To be fixed once possible
        • Done -

          Activity

          Ascending order - Click to sort in descending order
          Permalink
          Indrasan Yadav logged work - 02/Jan/25 12:00 AM - edited
          • Time Spent:
            1 hour
             

            Dear @Bassem Sabbagh,

            As per our earlier discussion, kindly assign an AI DEV resource to implement a rule for parsing nodes as outlined below:

            Note: This rule will apply when the same node (NEName) appears with two different models. The first model will be "BTS5900" and the second one will be "BTS3900" (see example for reference).

            Rule: We need to parse only the node that comes with NEType="BTS5900" and ignore the one with NEType="BTS3900".

            Example: For the node (NEName="ARR0519-P1-HUB_SRAN-FON"), it appears in the dump with two different models: NEType="BTS5900" and NEType="BTS3900". We need to parse only the entry with NEType="BTS5900" and disregard the entry with NEType="BTS3900".

            Best regards,
            Indrasan

          Indrasan Yadav made changes -
          Field Original Value New Value
          Gantt Options Milestone (set to milestone: having a due date but zero effort)
          Planned Start 2025-01-06 24:00 (milestone: set planned start date to due date)
          Planned End 2025-01-06 24:00 (milestone: set planned end date to due date)
          Indrasan Yadav made changes -
          Summary Need To Implement Rule For Duplicate Node_Huawei Need To Implement Rule For Duplicate Node With Different Model_Huawei
          Indrasan Yadav made changes -
          Description Dear @Bassem Sabbagh,

          As per our earlier discussion, kindly assign an AI DEV resource to implement a rule for parsing nodes as outlined below:

          Note: This rule will apply when the same node (NEName) appears with two different models. The first model will be "BTS5900" and the second one will be "BTS3900" (see example for reference).

          Rule: We need to parse only the node that comes with NEType="BTS5900" and ignore the one with NEType="BTS3900".

          Example: For the node (NEName="ARR0519-P1-HUB_SRAN-FON"), it appears in the dump with two different models: NEType="BTS5900" and NEType="BTS3900". We need to parse only the entry with NEType="BTS5900" and disregard the entry with NEType="BTS3900".

                  





          Best regards,
          Indrasan

          Indrasan Yadav made changes -
          Assignee Indrasan Yadav [ iyadav ] Bassem Sabbagh [ bsabbagh ]
          Bassem Sabbagh made changes -
          Assignee Bassem Sabbagh [ bsabbagh ] Sandya Sharma [ ssharma ]
          Hide
          Permalink
          Bassem Sabbagh added a comment -

          Assigned to Sandhya to define the WL

          Show
          Bassem Sabbagh added a comment - Assigned to Sandhya to define the WL
          Indrasan Yadav made changes -
          Link This issue blocks ZKU-94 [ ZKU-94 ]
          Permalink
          Sandya Sharma logged work - 08/Jan/25 12:00 AM
          • Time Spent:
            4 hours
             

            work on the issue

          Hide
          Permalink
          Sandya Sharma added a comment -

          WL is one day.

          Show
          Sandya Sharma added a comment - WL is one day.
          Hide
          Permalink
          Bassem Sabbagh added a comment -

          to be started and delivered by 9-1

          Show
          Bassem Sabbagh added a comment - to be started and delivered by 9-1
          Indrasan Yadav made changes -
          Remaining Estimate 0 minutes [ 0 ]
          Time Spent 1 hour [ 3600 ]
          Worklog Id 258700 [ 258700 ]
          Indrasan Yadav made changes -
          Baseline Start 2025-01-06 24:00 (set baseline based of initial work logging)
          Baseline End 2025-01-06 24:00 (set baseline based of initial work logging)
          Indrasan Yadav made changes -
          Worklog Id 258700 [ 258700 ]
          Permalink
          Indrasan Yadav logged work - 09/Jan/25 12:00 AM
          • Time Spent:
            2 hours
             

            Validate the XML and data was coming wrong so again confirmed to @Sandya to fix it.
            again validate the revised XML and now it is parsing correctly.

          Permalink
          Sandya Sharma logged work - 09/Jan/25 12:00 AM
          • Time Spent:
            7 hours
             

            work on the issue

          Permalink
          Sandya Sharma logged work - 09/Jan/25 12:00 AM
          • Time Spent:
            1 hour
             

            fix the issue

          Indrasan Yadav made changes -
          Time Spent 1 hour [ 3600 ] 3 hours [ 10800 ]
          Worklog Id 258836 [ 258836 ]
          Hide
          Permalink
          Indrasan Yadav added a comment -

          Dear @Sandya, please commit the code for same as now issue has been fixed in shared XML (2025-01-09-05.30.41_ZainKsa)

          Show
          Indrasan Yadav added a comment - Dear @Sandya, please commit the code for same as now issue has been fixed in shared XML (2025-01-09-05.30.41_ZainKsa)
          Sandya Sharma made changes -
          Time Spent 3 hours [ 10800 ] 1 day, 2 hours [ 36000 ]
          Worklog Id 258837 [ 258837 ]
          Sandya Sharma made changes -
          Time Spent 1 day, 2 hours [ 36000 ] 1 day, 6 hours [ 50400 ]
          Worklog Id 258838 [ 258838 ]
          Sandya Sharma made changes -
          Time Spent 1 day, 6 hours [ 50400 ] 1 day, 7 hours [ 54000 ]
          Worklog Id 258840 [ 258840 ]
          Hide
          Permalink
          Sandya Sharma added a comment -

          commit done.

          Show
          Sandya Sharma added a comment - commit done.
          Sandya Sharma made changes -
          Assignee Sandya Sharma [ ssharma ] Indrasan Yadav [ iyadav ]
          Hide
          Permalink
          Indrasan Yadav added a comment -

          We are now closing this child JIRA as it pertains to an individual issue.

          As suggested by @Ahad, all code commit JIRAs will be covered under the parent JIRA.

          Show
          Indrasan Yadav added a comment - We are now closing this child JIRA as it pertains to an individual issue. As suggested by @Ahad, all code commit JIRAs will be covered under the parent JIRA.
          Indrasan Yadav made changes -
          Status To Do [ 10001 ] In Progress [ 3 ]
          Indrasan Yadav made changes -
          Status In Progress [ 3 ] Done [ 10000 ]
          Transition Time In Source Status Execution Times Last Executer Last Execution Date
          To Do To Do In Progress In Progress
          		8d 22m 1 Indrasan Yadav 10/Jan/25 3:54 AM
          In Progress In Progress Done Done
          		5s 1 Indrasan Yadav 10/Jan/25 3:54 AM
          Subversion JIRA

          Links Hierarchy

          		  Documentation

          Invalid license: EXPIRED

          Cancel

            People

            • Assignee:
              Indrasan Yadav
              Reporter:
              Indrasan Yadav
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Due:
                Created:
                Updated:
                Planned Start:
                Planned End:
                Actual Start:
                Date of Baselining:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 day, 7 hours
                1d 7h

                  Drag and Drop