Max number of listeners and / or behaviours?

Fabian_b6hasv

Hello,
I have a question about the number of listener, or behavior.
Is there a recommendation on a maximum number of listeners that should not be exceeded so that the system runs without any problems?
I know that you should group many listeners together if possible. Also you can limit the action range by mapping. But if you would combine everything in one listener, the effort for the code review is consequently bigger.
The same question would be with the Behaviour.

Kind regards

Nic Brough -Adaptavist-

There's no easy number or simple rule that would let you come up with one.

The only answer is "stop adding new ones when you believe they're starting to have an effect on performance".

Each listener and Behaviour has an overhead in that they need to do something when they're triggered, but a long listener that does a lookup and a batch update of linked issues, imposes more load than 10 listeners that just write a line to a log.  All 11 of them have the same overhead.  Grouping listeners together is a good idea as long as you can write efficient code for them, it reduces the overhead, but there's a balance to be had with simplicity.

So, while 1,000 listeners might well be "too many" in one Jira system, another might be fine with 10,000.  It depends on what they're doing, not how many there are.