We have a ScriptRunner plugin that includes a postfunction that will, under certain circumstances, initiate an additional transition for an issue.
For example, imagine there's an issue that's currently in Status A. A user initiates a transition, T0, to Status B. A post-function for T0 determines that the issue should in turn, initiate another transition, T1, to Status C. To the user, Status B is effectively skipped.
However, upon doing so, the issue Status is B despite the fact that both the issue history and currently available transitions suggest the issue in in Status C. And the Integrity Checker reports the following for the issue:
"The current step associated with the workflow entry with id 20373 has an incorrect stepId. (JRA-4539)"
The issue is resolved by running the Fix. But I'd like to know *why* this is happening in the first place. The postfunction is the last item in the list and therefore, should work.
Has anyone else run into a problem like this?