Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-1062

If All SLA is not Appearing after Issue is Created, "SLA Modified" info will appear.

XMLWordPrintable

      NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.

      Steps to Reproduce:

      1. Create a Service Desk Project.
      2. Go to SLA tab.
      3. Create a new Metrics called "Test"
      4. Specify the settings as shown below:
      5. Save it.
      6. Raise a Request Type from the Customer Portal.

      Expected Result:
      As there is no SLA that have been modified, the SLA page will stays the same.

      Actual Result:
      There will be an Info that SLA have been modified and a button to update it.

      Notes:

      • This will be only happening when all of the SLA is not appearing at first.
      • When there SLA is appearing in the future:
        SLA appear in future means SLA that is starts counting only when for example "Entered Status: Waiting for customer". The SLA will only count the time when the ticket entered 'Waiting for customer'.

        If there is tickets that have yet to enter this 'Waiting For Customer' status, the SLA update notification will be shown. If all ticket already entered the 'Waiting For Customer' status, the SLA update notification will be gone.

        1. Selection_102.png
          Selection_102.png
          14 kB
        2. SLA.PNG
          SLA.PNG
          63 kB
        3. SLA2.PNG
          SLA2.PNG
          7 kB

          Form Name

            [JSDSERVER-1062] If All SLA is not Appearing after Issue is Created, "SLA Modified" info will appear.

            Owen made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2304618 ] New: JAC Bug Workflow v3 [ 3126294 ]
            Owen made changes -
            Symptom Severity Original: Minor [ 14432 ] New: Severity 3 - Minor [ 15832 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 2058481 ] New: JSD Bug Workflow v5 - TEMP [ 2304618 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2055727 ] New: JSD Bug Workflow v5 [ 2058481 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 1956124 ] New: JSD Bug Workflow v5 - TEMP [ 2055727 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v4 [ 1615451 ] New: JSD Bug Workflow v5 [ 1956124 ]
            jonah (Inactive) made changes -
            Description Original: *Steps to Reproduce*:
            # Create a Service Desk Project.
            # Go to SLA tab.
            # Create a new Metrics called "Test"
            # Specify the settings as shown below:
            !SLA.PNG|thumbnail!
            # Save it.
            # Raise a Request Type from the Customer Portal.

            *Expected Result*:
            As there is no SLA that have been modified, the SLA page will stays the same.

            *Actual Result*:
            There will be an Info that SLA have been modified and a button to update it.
            !SLA2.PNG|thumbnail!

            *Notes*:
            * This will be only happening when all of the SLA is not appearing at first.
            * When there SLA is appearing in the future:
            SLA appear in future means SLA that is starts counting only when for example "Entered Status: Waiting for customer". The SLA will only count the time when the ticket entered 'Waiting for customer'.
             !Selection_102.png|thumbnail!
            If there is tickets that have yet to enter this 'Waiting For Customer' status, the SLA update notification will be shown. If all ticket already entered the 'Waiting For Customer' status, the SLA update notification will be gone.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-1062].
              {panel}

            *Steps to Reproduce*:
            # Create a Service Desk Project.
            # Go to SLA tab.
            # Create a new Metrics called "Test"
            # Specify the settings as shown below:
            !SLA.PNG|thumbnail!
            # Save it.
            # Raise a Request Type from the Customer Portal.

            *Expected Result*:
            As there is no SLA that have been modified, the SLA page will stays the same.

            *Actual Result*:
            There will be an Info that SLA have been modified and a button to update it.
            !SLA2.PNG|thumbnail!

            *Notes*:
            * This will be only happening when all of the SLA is not appearing at first.
            * When there SLA is appearing in the future:
            SLA appear in future means SLA that is starts counting only when for example "Entered Status: Waiting for customer". The SLA will only count the time when the ticket entered 'Waiting for customer'.
             !Selection_102.png|thumbnail!
            If there is tickets that have yet to enter this 'Waiting For Customer' status, the SLA update notification will be shown. If all ticket already entered the 'Waiting For Customer' status, the SLA update notification will be gone.
            jonah (Inactive) made changes -
            Link New: This issue relates to JSDCLOUD-1062 [ JSDCLOUD-1062 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: cqt New: affects-cloud affects-server cqt
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v2 [ 1602209 ] New: JSD Bug Workflow v4 [ 1615451 ]

              Unassigned Unassigned
              jrahmadiputra Julian (Inactive)
              Affected customers:
              4 This affects my team
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: