When a workfolw step is executed using script in JIRA,the reporter is being set to null value even though there is no post function implemented for the same.

[GabrielleJ]

Can you check the "History" tab if someone/something changed it? Any other cron scripts/plugins you have installed that might cause this?

[pankaj hooda]

HI Gabrielle, I have made a filter which is used in a jelly script and in that jelly script all the issues in that filter are made to go through a specified transition with certain post functions in that transition. The entire process has been running finr for about two year without any issue but it started giving me this reporter null issue from yesterday only.

[Nic Brough -Adaptavist-]

Gabrielle is asking you to check the issue history for clues - where exactly does the reporter get unset? Is it in the same group as all the other changes in the transition or is it shortly before or after?

[Nic Brough -Adaptavist-]

Do you have other post-functions that might be setting the reporter to unassigned?

You've not given us your script either, so we can't help you if there are any bugs in that.

[pankaj hooda]

Hi Nic, There are about 5-6 post functions in that workflow transition but none of them sets the reporter to null. It is automatically getting set to null .The script was running fine for about two years but suddenly it started giving this issue .

[Nic Brough -Adaptavist-]

Ok, what are these functions, and what's the order? (I know most are standard system things, but it's worth checking) There's also the very obvious question - what changed at the time this problem started happening?

[Nic Brough -Adaptavist-]

Something has changed, it must have, for the change of behaviour. Postfunctions look ok, but I'd have a very close look at the ser "sla" next - has someone changed the user or their effective permissions in the project?

[pankaj hooda]

As the reporter field hasn't been changed in post function,it should not be null but should have the original value as its reporter.