SLA Bug in Service Desk Catalog

I've just found a bug regarding SLAs specifically in requests created through the Service Catalog Templates. First, it seemed as though the SLAs didn't work at all with requests created in the Service Catalog. When I created a test request, the Priority would set properly based on the Urgency and Impact because of the Priority Matrix. Please see this screenshot:

Notice that the Urgency, Impact, and Priority are set, yet the DueBy Date is not setting. Here is also proof that I have the SLA set up to pick up "5 Days" priority requests (for example) to set the SLA to 5 days:

When I created a new Service Catalog Template, in which I set a new SLA rule of 3 days WITHIN the template, the SLA rules start working. See example:

Notice the Priority is set to 4 Hours because of the Priority Matrix, but the SLA of 3 days within the ticket overrides. I need the SLA to set properly in requests created through Service Catalog Template based off of the SLA rules set out for incident requests (without having to set custom new SLAs in the templates themselves).

Please advise,

Jeff