Reporter automatically changed in the issue 'is blocked by'

[PIERSON Cédric]

Dear all, 

I discover a 'strange' behaviour in Jira.

A user change the reporter to one issue, and the other which is linked by the ' is blocked by' has the reporter changed too ....even if the user has no right to modify the reporter on the linked issue....

I have checked all automation rules, script,  I didn't find the root cause.

Did you have such a behaviour on your side?

[Trudy Claspill]

Hello @PIERSON Cédric 

That is not a native behaviour of Jira.

It could be caused by an Automation Rule, or a Listener, or a function provided by a plugin such as a Behaviour from the ScriptRunner plugin.

Without knowing what plugins you have on your instance, we can't suggest what might be causing it.

[Matt Parks]

I can confirm that this is not out of the box behavior.

@PIERSON Cédric If you look at the history of the 'is blocked by' issue, is the user that changed the reporter the same as the user that changed it on the original issue

[PIERSON Cédric]

Thanks a lot for your answer.

We have scriptrunner and automation rules as plugin , but I have checked all rules, even disable it on non prod environment , and the behaviour is the same.

I will check listener and behaviour, and give you a feedback.

@Matt Parks : I confirm that the new 'user' as reporter will be the same in the 'is blocked issue' , and only for the link 'is blocked by' , for the other link nothing happen.

Thanks a lot for your message.

Cédric

[PIERSON Cédric]

Dear all, I finally found our bug...

It was a configuration inside the Element Copy&Sync -> Synchronization ....

I have fix it. 

Thanks a lot for your help and advice.

Regards,

Cédric