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?
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.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs