How many post functions is too many?

Andrew ONeill

Hello everyone!

 

I have a use case where eventually we may have up to 200 post functions on a single transition and I am a bit concerned that eventually it may cause issues. As anyone had this many post functions on a transition.

 

The reason for the large number of post functions is we use Xporter to create a document for a medication questionnaire and of course each questionnaire is different depending on the medication that has been selected. So we have to make a post function for each specific medication. Only one of them will trigger, but there could be up to 200 of them eventually. 

 

Does anyone have any experience with something like this?

Joshua Sneed Contegix

HI Andrew,

That is a lot. I've had 96 scripted post functions (PF) on a transition (Jira server 8.5) that were triggered based on several fields selected during creation. Expected use was that options in the fields selected would trigger less than 5 PFs and occasionally would see more, but never all of them. My tests were for all 96 every time. There was a noticeable delay when transitioning/updating the issue of about ~15 seconds.

To limit user and resource impact, I would probably move this automation away from the workflow and into something that based off the issue updated event plus a condition to limit it to the project/issues needed. Cheers!