Customer request status does not match?

[Duje]

Hi everyone,

2018-08-20 11:59:25,184 automation-rule-executor:thread-4 WARN automation     [feature.customer.request.CustomerRequestInternalManagerImpl] The first customer request status found, does not appear to match the actual issues current customer request status. Attempt a re-sort operation before return results

I have ran all of the integrity checker functions, and even checked the states in the database, can not find the issues that would cause problems.

I have ran through Automation for JIRA rules and regular Service Desk automation rules, but I can not either find errors. 

What might be causing this if not inconsistent workflow states?

[Administrator]

I have had the same problem using the 'Checklist for JIRA' and 'Misc Workflow Extensions' addon.

I have asked the static checklist during issue resolution and for every checked item I create an entry in the Labels field. If the issue was reopened I delete the Labels field using the postfunction 'Set field value (JMWE add-on)'.

After upgrading the 'Misc Workflow Extensions' addon up to version 5.7.0 and using the postfunction 'Clear field value (JMWE add-on)' to delete the Labels field the problem does no more occur.

Maybe this help you to solve your issues.

[David]

 Thanks for the advice, I am using the checklist addon so there could be a correlation there. I'll look into this.

[Michael Bachmann]

I have the same problem and even receive the log entry when opening an issue :(

2018-10-26 08:49:21,460 https-jsse-nio-8443-exec-136 WARN *** /browse/SD-15968 [c.a.s.i.f.customer.request.CustomerRequestInternalManagerImpl] The first customer request status found, does not appear to match the actual issues current customer request status. Attempt a re-sort operation before return results

 I don't have "Checklist for JIRA" installed, but use JWME. I checked some transitions but there are just so many...

Where you able to figure this out?

[David]

 I was not able to figure it out yet, it isn't causing any adverse effects as far as I can tell, so it's on the back burner until the day comes around where I have time to look into this.

[David]

You ever solve this? I'm having the same issue.

[Duje]

Unfortunately no,the atlassian-servicedesk.log is full of it still.