No other steps in the (customa) workflow have this problem. I've added sd.step.key for each workflow and sd.tour.resolve.step = true for all steps to Resolved. There is no automation rule for issues in Resolved.
Anyone seen this beast?
version 3.3.
Hi Mark,
Sorry to hear that you have encountered this problem. I believe that this is a documented bug in Service Desk. Please see https://jira.atlassian.com/browse/JSDSERVER-4932 for more details on this.
The good news is that a refresh of the browser should then immediately show the correct status. I agree that is should not be showing a NULL here, but we don't have any other work-around for this particular problem at this time. I would recommend watching that bug ticket for updates as to when this might be fixed in Jira Service Desk.
Regards,
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.