I've seen transitions with almost 100. They're very slow, but still work.
On top of the standard five, I would try to avoid adding more than 10-12 simple ones, or 2-3 complex (or dependent on other systems) ones if you want the transition to execute before your people get frustrated and impatient.
From a management point, working through a list of 70 "clever" things someone things they might need to do on a transition is a nightmare. I'd rather have a couple that do some minimal stuff, and one that offloads the rest of the clever things as a single "Oi! This just happened" to some middleware layer.
@Payne - yes, scary, and horrid to try to untangle.
@Andy J - I have no "simple" guidelines, it is absolutely "what will work for this team". Do what works well for your people (not you as an admin - our job is not to be happy, but to enable other people to work well together, even when that particular config is really bad)
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events