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

        Activity

        Indrasan Yadav made changes -
        Status In Progress [ 3 ] Done [ 10000 ]
        Indrasan Yadav made changes -
        Status To Do [ 10001 ] In Progress [ 3 ]
        Sandya Sharma made changes -
        Assignee Sandya Sharma [ ssharma ] Indrasan Yadav [ iyadav ]
        Sandya Sharma made changes -
        Time Spent 1 day, 6 hours [ 50400 ] 1 day, 7 hours [ 54000 ]
        Worklog Id 258840 [ 258840 ]
        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 3 hours [ 10800 ] 1 day, 2 hours [ 36000 ]
        Worklog Id 258837 [ 258837 ]
        Indrasan Yadav made changes -
        Time Spent 1 hour [ 3600 ] 3 hours [ 10800 ]
        Worklog Id 258836 [ 258836 ]
        Indrasan Yadav made changes -
        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 -
        Remaining Estimate 0 minutes [ 0 ]
        Time Spent 1 hour [ 3600 ]
        Worklog Id 258700 [ 258700 ]
        Indrasan Yadav made changes -
        Link This issue blocks ZKU-94 [ ZKU-94 ]
        Bassem Sabbagh made changes -
        Assignee Bassem Sabbagh [ bsabbagh ] Sandya Sharma [ ssharma ]
        Indrasan Yadav made changes -
        Assignee Indrasan Yadav [ iyadav ] Bassem Sabbagh [ bsabbagh ]
        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 -
        Summary Need To Implement Rule For Duplicate Node_Huawei Need To Implement Rule For Duplicate Node With Different Model_Huawei
        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)

          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