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

      Hello,

      I'm setting a Jira Service Desk instance (hosted on our servers), everything's fine except SLA metrics creation.

      In Project administration > SLA :

      • click on new metric
      • check in "Start" column : every workflow statuses should be available with "Entered status : x " option (screenshot 1)
      • on my instance, only one status (used in only one workflow) is available (screenshot 2)

      I've tried to restart server, enable disable plugins with sla in their name : no effect.
      If I create a new project from Service Desk template, statuses are available.

      Thanks for any help.

          Form Name

            [JSDSERVER-3905] Missing "Entered status : " in SLA metrics setup screen

            Hello JSD 4.5.2 here, same.

            In my staging instance, I have all the "Entered status" but in prod nothing.
            Will try a reindex.

            Sylvain Leduc added a comment - Hello JSD 4.5.2 here, same. In my staging instance, I have all the "Entered status" but in prod nothing. Will try a reindex.

            We have the same issue in two of our instances, can't see any options for statuses or comment in Pause.

            JIRA Service Desk 4.2.2 and 3.15.3

            Andres Santamaria [Eficode] added a comment - - edited We have the same issue in two of our instances, can't see any options for statuses or comment in Pause. JIRA Service Desk   4.2.2  and 3.15.3

            Hi Trey and Damien

            I have the same problem. I opened a issue on Jira Support But it do not allow to open as a bug.

            Every time redirect to the main website. 

            1. JRASERVER-68629

            I did the re-index but it still to not return on status "aguardando expiração".

            The filter to stop the SLA do not return the status.

             On workflow it is nothing wrong, and it is published already.

            Regards.

             Daniel Soares

            Daniel Soares added a comment - Hi Trey and Damien I have the same problem. I opened a issue on Jira Support But it do not allow to open as a bug. Every time redirect to the main website.  JRASERVER-68629 I did the re-index but it still to not return on status "aguardando expiração". The filter to stop the SLA do not return the status.  On workflow it is nothing wrong, and it is published already. Regards.  Daniel Soares

            Hi mathieu1594142215,
            Could you create a support ticket at https://support.atlassian.com? 
            That way we can provide you with support specific to your circumstances and with higher security. 
            The credentials should be the same as for this site (https://jira.atlassian.com).
            Thanks,
            JIRA Service Desk Team

            Trey Brisbane (Inactive) added a comment - Hi mathieu1594142215 , Could you create a support ticket at https://support.atlassian.com?   That way we can provide you with support specific to your circumstances and with higher security.  The credentials should be the same as for this site ( https://jira.atlassian.com ). Thanks, JIRA Service Desk Team

            If this can be of any help, atlassiant-servicedsk.log shows :

            2016-06-10 15:13:56,547 http-nio-8080-exec-14 WARN user 913x4451x1 5ex0a2 ip /rest/servicedesk/1/servicedesk/PRJ/sla/conditions/available [internal.sla.condition.ConditionFactoryServiceImpl] Plugin module com.atlassian.servicedesk:status-sla-condition-factory threw exception null

            Restarting this module doesn't change anything.

            Damien Mathieu added a comment - If this can be of any help, atlassiant-servicedsk.log shows : 2016-06-10 15:13:56,547 http-nio-8080-exec-14 WARN user 913x4451x1 5ex0a2 ip /rest/servicedesk/1/servicedesk/PRJ/sla/conditions/available [internal.sla.condition.ConditionFactoryServiceImpl] Plugin module com.atlassian.servicedesk:status-sla-condition-factory threw exception null Restarting this module doesn't change anything.

              Unassigned Unassigned
              3a793136531e Damien Mathieu
              Affected customers:
              4 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated: