Does Committing Updates in Portfolio trigger an Event?

[Brendan Byers]

Using Script runner we have some script listeners that automatically copy certain values from one field to another whenever an Issue updated Event is triggered.
However I recently noticed that when updating fields in Portfolio and then committing those fields the scripts are not triggered.

Is Portfolio not throwing this event as part of committing changes?

[Earl McCutcheon]

Hello Brendan,

I know there are some conflicts in the create transition that I am aware of in portfolio covered in the following feature request relating to how portfolio temporarily stores data before committing, and you may be running into a similar result on your scripted listener:

• https://jira.atlassian.com/browse/JPOSERVER-2236

We primarily see this conflict occur on the parent to child issue linking for the portfolio hierarchy structure like epic link between the epic and story.

Can you provide some additional details on how you have this configured and the script you are using

[Brendan Byers]

I chatted with Attlassian support and they directed me to this already logged issue which better describes the problem:

https://jira.atlassian.com/browse/JPOSERVER-2268

As near as I can tell if you edit only fields introduced by Portfolio (such as Team) and commit them no Issue Updated Event is triggered.

I tried this with even a simple "Hello World" script which did nothing but dump information to the logs and it would only trigger if Jira fields like Fix Version were edited at the same time as Team.

Hopefully this can be fixed in the near future.

[Artem Grotskyi]

Unfortunately, it's not fixed yet. :(
We also need this feature...