Write Field On Linked Issues isn't triggering an Issue Updated event?

[Aggelos Paraskevopoulos [Cententia]]

We've got a problem report from a customer saying that the "Write Field On Linked Issues" is not triggering the "Issue Updated" event on the linked issues. They have recently upgraded to 2.2.36 and tried to replace "Update on Transition" post-function with the JWT one.

Any ideas?

BR/Aggelos.

[Fidel Castro Armario]

Hi @aggelosp,

Currently it doesn't trigger the "Issue Updated" event. I will try to add it as an option to the post-function.

[Aggelos Paraskevopoulos [Cententia]]

Hi @fcarmario ,

Back in issue #338, you wrote,

The new version is triggering an "Issue Updated" event each time a field is updated. I don't know yet whether it will be the definitive solution, because I haven't yet investigated possible problems when many fields are updated on a same issue, because it will triggering more than one event on a same issue.

So you finally reverted this?

[Fidel Castro Armario]

You are right, Aggelos. It hasn't been reverted. Sorry, I said that from memory.

I have checked the code, and the event should be triggering. I will try to reproduce the problem and investigate the cause. I will keep you informed.

[Aggelos Paraskevopoulos [Cententia]]

Hi @fcarmario,

Any news about this?

[Fidel Castro Armario]

Hi @aggelosp,

In version 2.2.37_beta_4 I have added a new optional parameter for enabling email notifications to post-functions Write field on issues returned by JQL Query or Issue List and Write field on linked issues or subtasks.

Please, let me know whether it solves your problem.

[Aggelos Paraskevopoulos [Cententia]]

Hi @fcarmario ,

Customer reported the option works just fine.

Thanks!

[Fidel Castro Armario]

Fixed in just released version 2.2.37.

[Aggelos Paraskevopoulos [Cententia]]

Hi Fidel,

Another customer reported that the new option didn't work for "new comment", "attachment (only new attachments..)" virtual fields. Could you please check this? I've urged them to post here any further info that might help.

[konstantinos kontomaris]

Hello Fidel,

Following Aggelos' latest Comment, I attach here a couple of snapshots that might help.

As you can see, we have created a special w/f transition in order for Comments to be automatically "transfered" to other Issues that might be linked to the current Issue (that will be probably when someone wants to inform all the people involved in a case about a serious event that affects all)

The post-function works fine, as the submitted Comments are copied to all the linked Issues as "New Comments", however, the problem is that the stakeholders of the linked Issues don't receive any notifications about these (copied) Comments.

Testing shows that this (no-e-mail-notification) problem appears only when the "Target" field is one of the "JIRA Workflow Toolbox" 's "Virtual Fields" (such as: "new comment", "attachment (only new attachments..)", "last comments visibility restrictions" etc.). When we set any other ordinary CF (one that has a CF ID) as a "Target" field, an e-mail notification is sent normally.

You can find a detailed scenario at the attachments; I hope this will help

Best Regards Konstantinos

P.S. It seems that a "Issue Updated" event can be (is) triggered after the execution of the post-function, whereas a "Issue Commented" event is not.

[konstantinos kontomaris]

Adding here: JIRA version: 6.4.11 JIRA Workflow Toolbox version: 2.2.38

[Fidel Castro Armario]

Hi @aggelosp and @kontedimara,

I will try to support notifications for virtual fields in a future version of the plugin. Meanwhile, you can use virtual field "New comment (sends notification)", instead of "New comment" for solving the problem when copying comments.

[konstantinos kontomaris]

Thanks, Fidel!

This virtual Field already existed..? My apologies for haven't seen this..

Moreover, it would be great if at the next version you could add an option to choose whether to send (Comment) notifications internally OR globally: that would really serve the case where: 1) one of the linked Issues is a Service Desk Issue 2) an "internal" broadcast towards all the related Issues' stakeholders is necessary, while, on the other hand, 3) this "internal" broadcast should not be exposed to the external customer (Service Desk Customer) of the SD Issue

Thank you very much for your instant reply Thank you too, Aggelos for your help