Where a context macro is used, the trigger name and description fields do not resolve the macro correctly.

--Trigger--
Name: Filesystem {#FSNAME} is >{$WARNING_VOLUME_USAGE:"{#FSNAME}"} full: {ITEM.LASTVALUE}
Expression: {myhost.example.com:netapp.dfPerCentKBytesCapacity[{#FSNAME}].last()}>={$WARNING_VOLUME_USAGE:"{#FSNAME}"}

Description:
One: {$WARNING_VOLUME_USAGE:{#FSNAME}}
Two: {$WARNING_VOLUME_USAGE:{"#FSNAME"}}

--Host--
Macros:
{$WARNING_VOLUME_USAGE} = 87
{$WARNING_VOLUME_USAGE:/vol/KVM01} = 70

The item returns a value of 83, and the trigger alerts - but the name in the alert is:

Filesystem /vol/KVM01 is >87} full: 83 %

So clearly the macro override is being respected in the trigger expression, but just not resolving correctly in the name. The description also has this issue, and displays as:

One: 87}
Two: 87

Also tried using the context macro without quotes in the trigger name, but didn't resolve that either.