Details

    • Customer:
      OMAN-Tel

      Description

      7/10/2025:

      1. In GTM comments: Please ensure that the timestamp for each message/comment is displayed directly. This will help track the sequence and timing of updates more clearly.
      2. In logs: The name or identifier of the user who submitted the comment, along with the timestamp, should also be shown to maintain accountability and context.

      Please refer to the new attached images.

      Currently, only the latest comment submitted in GTM is visible in SRD. However, we require the full comment history to be displayed in SRD, similar to how it appears in GTM. Below picture GTMHistory attached.
      In addition,
      Any information entered in the “Additional Details” section should be properly saved and displayed in SRD UI. This ensures that when we revisit the request in the future, we can view all previously entered comments and context. Image attached from UI

        Activity

        Salem Dannawi made changes -
        Field Original Value New Value
        Gantt Options Milestone (set to milestone: having a due date but zero effort)
        Planned Start 2025-09-26 24:00 (milestone: set planned start date to due date)
        Planned End 2025-09-26 24:00 (milestone: set planned end date to due date)
        Khaled Khalil made changes -
        Assignee Khaled Khalil [ kkhalil ] Ayed Bada [ abada ]
        Ayed Bada logged work - 30/Sep/25 12:00 AM
        • Time Spent:
          1 day
           

          Add history service

        Ayed Bada logged work - 01/Oct/25 12:00 AM
        • Time Spent:
          4 hours
           

          test and commit

        made changes -
        Attachment SRD_COMMENT_HISTORY.sql [ 118814 ]
        Hide
        added a comment - - edited

        Hello,
        I have completed the implementation of the history display feature and committed the changes on the SRD project.
        Additionally, I’ve added the required SQL script that needs to be executed.

        The related patch is: 3.7.0.1354, and a restart is required after deployment.

        Best regards,

        Show
        added a comment - - edited Hello, I have completed the implementation of the history display feature and committed the changes on the SRD project. Additionally, I’ve added the required SQL script that needs to be executed. The related patch is: 3.7.0.1354, and a restart is required after deployment. Best regards,
        Khaled Khalil made changes -
        Status Opened [ 1 ] Pending Requirements [ 10300 ]
        Salem Dannawi logged work - 02/Oct/25 12:00 AM
        • Time Spent:
          1 hour, 30 minutes
           

          test the new CR on staging

        Ayed Bada made changes -
        Remaining Estimate 0 minutes [ 0 ]
        Time Spent 1 day [ 28800 ]
        Worklog Id 279204 [ 279204 ]
        Ayed Bada made changes -
        Baseline Start 2025-09-26 24:00 (set baseline based of initial work logging)
        Baseline End 2025-09-26 24:00 (set baseline based of initial work logging)
        Ayed Bada made changes -
        Time Spent 1 day [ 28800 ] 1 day, 4 hours [ 43200 ]
        Worklog Id 279205 [ 279205 ]
        Salem Dannawi made changes -
        Time Spent 1 day, 4 hours [ 43200 ] 1 day, 5 hours, 30 minutes [ 48600 ]
        Worklog Id 279224 [ 279224 ]
        Salem Dannawi logged work - 07/Oct/25 12:00 AM
        • Time Spent:
          1 hour, 30 minutes
           

          call with customer,
          understand the required,
          call with Ayed to clarify to him

        Ayed Bada logged work - 07/Oct/25 12:00 AM
        • Time Spent:
          2 hours
           

          start dev part

        Salem Dannawi made changes -
        Description Currently, only the latest comment submitted in GTM is visible in SRD. However, we require the full comment history to be displayed in SRD, similar to how it appears in GTM. Below picture GTMHistory attached.
        In addition,
        Any information entered in the “Additional Details” section should be properly saved and displayed in SRD UI. This ensures that when we revisit the request in the future, we can view all previously entered comments and context. Image attached from UI
        7/10/2025:


        1. In GTM comments: Please ensure that the timestamp for each message/comment is displayed directly. This will help track the sequence and timing of updates more clearly.
        2. In logs: The name or identifier of the user who submitted the comment, along with the timestamp, should also be shown to maintain accountability and context.

        Please refer to the new attached images.






        Currently, only the latest comment submitted in GTM is visible in SRD. However, we require the full comment history to be displayed in SRD, similar to how it appears in GTM. Below picture GTMHistory attached.
        In addition,
        Any information entered in the “Additional Details” section should be properly saved and displayed in SRD UI. This ensures that when we revisit the request in the future, we can view all previously entered comments and context. Image attached from UI
        Salem Dannawi made changes -
        Attachment User name in logs for return to AM action.png [ 119220 ]
        Attachment GTMTIME.PNG [ 119221 ]
        Salem Dannawi made changes -
        Time Spent 1 day, 5 hours, 30 minutes [ 48600 ] 1 day, 7 hours [ 54000 ]
        Worklog Id 279564 [ 279564 ]
        Ayed Bada logged work - 08/Oct/25 12:00 AM
        • Time Spent:
          4 hours
           

          compete dev and release the patch

        Khaled Khalil made changes -
        Status Pending Requirements [ 10300 ] Pending Design Session [ 10112 ]
        Assignee Ayed Bada [ abada ] Khaled Khalil [ kkhalil ]
        Khaled Khalil made changes -
        Status Pending Design Session [ 10112 ] Dev Scheduled [ 10014 ]
        Ayed Bada made changes -
        Status Dev Scheduled [ 10014 ] Implementation in progress [ 10016 ]
        Assignee Khaled Khalil [ kkhalil ] Ayed Bada [ abada ]
        Ayed Bada made changes -
        Status Implementation in progress [ 10016 ] To Be Released [ 10400 ]
        Hide
        Ayed Bada added a comment -

        Hello,
        I have successfully enhanced the GTM comments and logs by incorporating the required information, including timestamps, to improve traceability.
        The related patch is: 3.7.0.1358, and a restart is required after deployment.
        Best regards,

        Show
        Ayed Bada added a comment - Hello, I have successfully enhanced the GTM comments and logs by incorporating the required information, including timestamps, to improve traceability. The related patch is: 3.7.0.1358, and a restart is required after deployment. Best regards,
        Khaled Khalil made changes -
        Status To Be Released [ 10400 ] Ready for QA [ 10023 ]
        Assignee Ayed Bada [ abada ] Salem Dannawi [ sdannawi ]
        Ayed Bada made changes -
        Time Spent 1 day, 7 hours [ 54000 ] 2 days, 1 hour [ 61200 ]
        Worklog Id 279717 [ 279717 ]
        Ayed Bada made changes -
        Time Spent 2 days, 1 hour [ 61200 ] 2 days, 5 hours [ 75600 ]
        Worklog Id 279719 [ 279719 ]
        Salem Dannawi logged work - 09/Oct/25 12:00 AM
        • Time Spent:
          1 hour, 30 minutes
           

          test the new requirements in staging,
          still not finished from L3 side

        Ayed Bada logged work - 09/Oct/25 12:00 AM - edited
        • Time Spent:
          2 hours
           

          Pass userName in process for log part

        Salem Dannawi made changes -
        Status Ready for QA [ 10023 ] QA In Progress [ 10015 ]
        Salem Dannawi made changes -
        Time Spent 2 days, 5 hours [ 75600 ] 2 days, 6 hours, 30 minutes [ 81000 ]
        Worklog Id 279849 [ 279849 ]
        Ayed Bada logged work - 10/Oct/25 12:00 AM
        • Time Spent:
          2 hours
           

          Pass userName in process for log part

        Salem Dannawi logged work - 10/Oct/25 12:00 AM
        • Time Spent:
          30 minutes
           

          test after edit the patch from L3

        Salem Dannawi logged work - 13/Oct/25 12:00 AM
        • Time Spent:
          1 hour, 30 minutes
           

          test the new requested after implementing it on staging

        Salem Dannawi made changes -
        Time Spent 2 days, 6 hours, 30 minutes [ 81000 ] 3 days [ 86400 ]
        Worklog Id 280158 [ 280158 ]
        Ayed Bada made changes -
        Time Spent 3 days [ 86400 ] 3 days, 2 hours [ 93600 ]
        Worklog Id 280230 [ 280230 ]
        Ayed Bada made changes -
        Worklog Id 280230 [ 280230 ]
        Ayed Bada made changes -
        Time Spent 3 days, 2 hours [ 93600 ] 3 days, 4 hours [ 100800 ]
        Worklog Id 280231 [ 280231 ]
        Salem Dannawi made changes -
        Time Spent 3 days, 4 hours [ 100800 ] 3 days, 4 hours, 30 minutes [ 102600 ]
        Worklog Id 280752 [ 280752 ]
        Salem Dannawi logged work - 20/Oct/25 12:00 AM
        • Time Spent:
          1 hour
           

          call with Manal and Yusuf ( customer ) , and test all requested items

        Salem Dannawi made changes -
        Time Spent 3 days, 4 hours, 30 minutes [ 102600 ] 3 days, 5 hours, 30 minutes [ 106200 ]
        Worklog Id 280985 [ 280985 ]
        Hide
        added a comment -

        WL = 4 md for dev and testing

        Show
        added a comment - WL = 4 md for dev and testing
        Natnael Asfaw logged work - 09/Dec/25 12:00 AM - edited
        • Time Spent:
          30 minutes
           

          Apply script on prod

        Salem Dannawi logged work - 10/Dec/25 12:00 AM
        • Time Spent:
          2 hours
           

          check logs,
          reproduce same on staging,
          same issue on prod ! integration issue they are checking

        Ayed Bada logged work - 10/Dec/25 12:00 AM
        • Time Spent:
          4 hours
           

          Investigate and Fix production issue

        Salem Dannawi made changes -
        Time Spent 3 days, 5 hours, 30 minutes [ 106200 ] 3 days, 7 hours, 30 minutes [ 113400 ]
        Worklog Id 285614 [ 285614 ]
        Natnael Asfaw made changes -
        Time Spent 3 days, 7 hours, 30 minutes [ 113400 ] 4 days [ 115200 ]
        Worklog Id 285971 [ 285971 ]
        Natnael Asfaw made changes -
        Worklog Id 285971 [ 285971 ]
        Ayed Bada made changes -
        Time Spent 4 days [ 115200 ] 4 days, 4 hours [ 129600 ]
        Worklog Id 285995 [ 285995 ]
        Abir Messaikeh made changes -
        Status QA In Progress [ 10015 ] Closed [ 6 ]
        Resolution Fixed [ 1 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Opened Opened Pending Requirements Pending Requirements
        9d 3h 14m 1 Khaled Khalil 01/Oct/25 11:04 AM
        Pending Requirements Pending Requirements Pending Design Session Pending Design Session
        6d 23h 7m 1 Khaled Khalil 08/Oct/25 10:11 AM
        Pending Design Session Pending Design Session Dev Scheduled Dev Scheduled
        20s 1 Khaled Khalil 08/Oct/25 10:11 AM
        Dev Scheduled Dev Scheduled Implementation in progress Implementation in progress
        11s 1 Ayed Bada 08/Oct/25 10:11 AM
        Implementation in progress Implementation in progress To Be Released To Be Released
        10s 1 Ayed Bada 08/Oct/25 10:12 AM
        To Be Released To Be Released Ready for QA Ready for QA
        20m 21s 1 Khaled Khalil 08/Oct/25 10:32 AM
        Ready for QA Ready for QA QA In Progress QA In Progress
        1d 2h 9m 1 Salem Dannawi 09/Oct/25 12:42 PM
        QA In Progress QA In Progress Closed Closed
        75d 21h 51m 1 Abir Messaikeh 24/Dec/25 9:34 AM
        Subversion JIRA

        Links Hierarchy

         Documentation

        Invalid license: EXPIRED

          People

          • Assignee:
            Salem Dannawi
            Reporter:
            Salem Dannawi
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Due:
              Created:
              Updated:
              Resolved:
              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 - 4 days, 4 hours
              4d 4h

                Drag and Drop