• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Highest Highest
    • 1.2.4
    • 1.2
    • None

      Error: Workflow statuses details could not be saved is thrown when trying to change the status name.

      Affecting JIRA Service Desk 1.2. Please upgrade to JIRA Service Desk 1.2.4+ for the fix on this.

          Form Name

            [JSDSERVER-413] Workflow statuses details could not be saved

            This is fixed in version 1.2.4, which is now available at marketplace.atlassian.com

            Cheers,
            Gilmore

            Gilmore Davidson (Inactive) added a comment - This is fixed in version 1.2.4, which is now available at marketplace.atlassian.com Cheers, Gilmore

            Hi,

            I am having the same problem, Any news on when this will be released?

            Thanks

            Anand Unadkat added a comment - Hi, I am having the same problem, Any news on when this will be released? Thanks

            oli added a comment - - edited

            Hi,
            We have fixed this in our code and it will be available in an upcoming bug fix release.

            Thanks,
            Service Desk Team

            oli added a comment - - edited Hi, We have fixed this in our code and it will be available in an upcoming bug fix release. Thanks, Service Desk Team

            Hi, any updates on this? Can I at least get an expected release date?

            Lisa Schaffer added a comment - Hi, any updates on this? Can I at least get an expected release date?

            I need to go live with Service Desk soon and our workflows are VERY customised, and we need Service Desk to support this, else we cannot use it as a solution.

            Lisa Schaffer added a comment - I need to go live with Service Desk soon and our workflows are VERY customised, and we need Service Desk to support this, else we cannot use it as a solution.

            Hi,
            We are fixing the issue and will release the fix very soon.

            Thanks,
            Service Desk Team

            Panna (Inactive) added a comment - Hi, We are fixing the issue and will release the fix very soon. Thanks, Service Desk Team

            I get this error as well on JIRA 6.1.2 and SD 1.2.1.
            2014-03-18 14:15:19,665 ajp-bio-8009-exec-5 ERROR jasonsmith 855x7253x1 1126op 192.168.64.27 /rest/servicedesk/1/servicedesk-data/hd/request-type/4/workflow [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: Can not deserialize instance of java.util.ArrayList out of VALUE_STRING token
            at [Source: org.apache.catalina.connector.CoyoteInputStream@5db21cb0; line: 1, column: 1]
            org.codehaus.jackson.map.JsonMappingException: Can not deserialize instance of java.util.ArrayList out of VALUE_STRING token

            Deleted Account (Inactive) added a comment - I get this error as well on JIRA 6.1.2 and SD 1.2.1. 2014-03-18 14:15:19,665 ajp-bio-8009-exec-5 ERROR jasonsmith 855x7253x1 1126op 192.168.64.27 /rest/servicedesk/1/servicedesk-data/hd/request-type/4/workflow [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: Can not deserialize instance of java.util.ArrayList out of VALUE_STRING token at [Source: org.apache.catalina.connector.CoyoteInputStream@5db21cb0; line: 1, column: 1] org.codehaus.jackson.map.JsonMappingException: Can not deserialize instance of java.util.ArrayList out of VALUE_STRING token

              Unassigned Unassigned
              d706abbae7c8 Lisa Schaffer
              Affected customers:
              5 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: