Script-Runner: "Issue updated" not triggered for sub task.

[Marcus Krejpowicz]

Hello

I am using Jira Cloud and I was trying to add a adaptavist script listener which sums up all time estimates of the parents subtasks and writes it back to the parent but I've noticed that the "Issue updated" event is not fired for sub-tasks.

Is there a special setting that will enable events for subtasks or is it not possible?

Kind Regards

Marcus

[Nic Brough -Adaptavist-]

What are you doing to the sub tasks that avoids firing issue updated?

[Marcus Krejpowicz]

I changed the description and the original estimated time.

For normal issues it is fireing, but not for sub tasks. 

[Stephen Jackson]

Actually Marcus, I ran into the same issue myself but just realised the issue is a little different. Although i initially believed that the "Issue Updated" event was not firing when time was being logged to a Sub-task, I just found out that the issue does fire - it just takes a really long time.

For me, if i update a normal task, the processing of the event completes in under 20s. If i make the same change to a sub-task, the event doesn't appear to trigger for around 5 minutes - which is more than enough time for me to blame my own script for not catching/handling the event properly and then not noticing that it has fired.

Perhaps that same thing is happening for you? Personally I would still typify this behaviour as being a bug ...

[Marcus Krejpowicz]

Hey Stephen, thank you for pointing this out. I haven't looked into the issue again, but I will try it out. 5 minutes would be okay for me although this isn't the expected behaviour. I guess it has something to do with the event queue on the cloud service.