Reporter automatically changed in the issue 'is blocked by'

PIERSON Cédric February 22, 2024

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?

1 answer

1 vote
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 22, 2024

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
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 22, 2024

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 February 22, 2024

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 February 29, 2024

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

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
9.4.15
TAGS
AUG Leaders

Atlassian Community Events