SLAs do not include transaction names, SLA goals, or actual response times. I have validated SLAs are setup properly in the Analysis tool and they do report correctly. Additionally, Jenkins reports the test Passed even though two of the SLAs reported failures.

03/06/2014 14:36:42 Running: C:\CD_LR\scenarios\CD_Scenario.lrs
Cleaning up the environment...
Preparing scenario C:\CD_LR\scenarios\CD_Scenario.lrs for execution.
Load Generator localhost connected
Starting scenario...
============================================================================
Analyzing results...
Analysis Results:

SLA report:
================================
Full Name : Transaction Response Time (Average)
Measurement : AverageTRT
CriteriaMeasurement Value : None
LoadThresholds value :
status : Failed
================================
================================
Full Name : Transaction Response Time (Average)
Measurement : AverageTRT
CriteriaMeasurement Value : None
LoadThresholds value :
status : Failed
================================
================================
Full Name : Transaction Response Time (Average)
Measurement : AverageTRT
CriteriaMeasurement Value : None
LoadThresholds value :
status : Passed
================================

Error(s) summary:
0 ignored , 0 errors

Test result: Passed
03/06/2014 14:43:34 Test complete: C:\CD_LR\scenarios\CD_Scenario.lrs