I implemented a AbstractEventIssueListener. And I am listening to com.exalate.api.domain.trigger.EXALATED Event.That is necessary because a postfunction must be executed after Exelate finished !!
Ok. The postfunction reads some values from issue fields and then just makes a REST call to a server.
Now the strange thing occurs. To read the value from the issue we use a normal Jira Function which works in many different postfunctions. But now if update the field value of the issue, and trigger exalate which when finished triggers the postfuntion still reads the old value and not the updated value. How can that be ?? We already invested many days to find out the problem. One guess is Exalate. Maybe Exalate caches the old value of the issue. But it is really only a guess. We have no clue.
I implemented a AbstractEventIssueListener. And I am listening to com.exalate.api.domain.trigger.EXALATED Event.That is necessary because a postfunction must be executed after Exelate finished !!
Ok. The postfunction reads some values from issue fields and then just makes a REST call to a server.
Now the strange thing occurs. To read the value from the issue we use a normal Jira Function which works in many different postfunctions. But now if update the field value of the issue, and trigger exalate which when finished triggers the postfuntion still reads the old value and not the updated value. How can that be ?? We already invested many days to find out the problem. One guess is Exalate. Maybe Exalate caches the old value of the issue. But it is really only a guess. We have no clue.