The same game as before, I'm drawing heavily on a swarm of small (1k-sized) survey ships for all geo and grav survey duties. I designed a (cheap) jump tender for their size, and placed one at every jump point, and clicked the "Assume Fleet is Jump-Capable". However, the surveyors entered a system whose JP was being stabilized, and when they finished their work they couldn't find their way out. I checked that the jump tender was placed at the entry point, tried again, and they continued complaining. I ordered them to move elsewhere and they went through the JP with no problem at all. I believe this "Assume Fleet is Jump-Capable" setting is not working. I wasn't tracking where the surveyors went so I can't be absolutely sure, but it seems they only plotted routes through JPs that were at least partially stabilized.
I couldn't find any report about this, either as a bug or feature. I'll try to reproduce this later in a new clean game.
EDIT: The surveyors are all using default orders to either geosurvey bodies in the system or do gravsurvey, according to their type, then proceed to another system needing surveying. That's my attempt to automate the surveying, with a dozen of FAC-sized survey craft of each type in a 10% survey speed game. However, when all survey is done in a border system, the survey craft ignore the jump tender in the JP and complain they can't apply the default orders, no matter whether the "Assume Fleet is Jump-Capable" is set or not.
I've also verified that when one survey craft completed their job and chose another system to go to, they'd cross my entire map for months to go to another system through a path connected with stabilized JPs, rather than cross a single JP with a jump tender available.
Adding a standard jump engine would require a full redesign and lots of refits, and would go counter the idea I'm following in this game. So, in order to avoid lots of micromanaging surveyors, I've now edited the DB (oops) to have a new miniaturized jump engine specifically for the survey craft, SM-edited their designs to include it, and I'm now waiting to see if they'll finally go to the closest system to do their jobs.
It's quite possible I misunderstood the meaning of the "Assume Fleet is Jump-Capable", and that it wasn't meant to apply to default orders... If so, please, Steve, could you consider it for a future version?
SJW: "Assume Fleet is Jump-Capable" is used to filter potential destinations when using Fleet Auto-route.