Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,460,148
Community Members
 
Community Events
176
Community Groups

Does Committing Updates in Portfolio trigger an Event?

Edited

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?

1 answer

0 votes

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:

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

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.

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

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events