Bug 43364

Summary: changed behaviour of ifcontroller in version 2.3?
Product: JMeter - Now in Github Reporter: Christoph <christoph.schragen>
Component: MainAssignee: JMeter issues mailing list <issues>
Status: RESOLVED FIXED    
Severity: enhancement    
Priority: P2    
Version: 2.3   
Target Milestone: ---   
Hardware: Other   
OS: other   

Description Christoph 2007-09-12 07:33:13 UTC 
hi,
i just noticed that the behaviour of the if-controller changed from version 2.2 
to 2.3.
the condition is now only evaluated for the first time. in jmeter 2.2, this 
condition was evaluated for all samples within the if-controller.
if found that this behaviour was practically... i think it would be great if 
the if-controller would have an option "evaluate for all children" were one can 
enable the old behavior of the if-controller.

greets,
  chris
Comment 1 Sebb 2007-09-12 10:22:32 UTC 
Yes, the behaviour was fixed in Bug 41612.

But it should be possible to add an option to enable the original behaviour.
Comment 2 Sebb 2007-09-19 15:12:48 UTC 
Added to SVN (rel-2.2) in r577455
Comment 3 Sebb 2007-09-19 15:44:11 UTC 
Copied to trunk in SVN r577462
Comment 4 The ASF infrastructure team 2022-09-24 20:37:40 UTC 
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2007