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

Users creating issues through JIRA UI rather than SD do not get SLA value correctly applied

    XMLWordPrintable

Details

    • Bug
    • Resolution: Answered
    • Low
    • None
    • None
    • None
    • None

    Description

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

      The SLA details only get set if using the SD UI, if using any other method (JIRA UI, email...), the values are not set. This leaves issues in very different SLA statuses.

      Attachments

        1. created-by-email.png
          12 kB
          Andy Brook [Plugin People]
        2. created-by-jira-ui-not-sd.png
          12 kB
          Andy Brook [Plugin People]
        3. Screen Shot 2013-11-06 at 1.49.43 PM.png
          49 kB
          Michael Ruflin
        4. Screen Shot 2013-11-06 at 1.49.47 PM.png
          62 kB
          Michael Ruflin
        5. sla-details.png
          10 kB
          Andy Brook [Plugin People]

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. JSDSERVER-38 As an admin I want Service Desk to recognise issues created by Mail Handlers and through the standard Create Issue

          • Low - Low priority issues
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JSDCLOUD-125 Users creating issues through JIRA UI rather than SD do not get SLA value correctly applied

          • Low - Low priority issues
          • Closed

          Activity

            People

              Unassigned Unassigned
              340ad212567f Andy Brook [Plugin People]
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync