Problem description: In case if a host has both macro (for example {$TEST}) and macro with context (like {$TEST:regex:"x"}) and then this macro is used in trigger expression or in operational data, then it is possible that the context macro will be resolved with plain macro value in the event details form. To observe the problem, please follow the steps below.{}

Steps to reproduce:

1. Create host with the following macros:
   1. {$TEST} =>33
   2. {$TEST:regex:"x"} => 15
2. Create a trapper item with key "trap" on this host
3. Create a trigger that will use the TEST macro in its operational data and in its function in the following way:
   1. Operational data =>Some text {$TEST:regex:x}
   2. {<host name>:trap.last()}

      >{$TEST:regex:x}

4. Send a value to the trapper item, that would be higher then the value of the context macro but lower than the value of the plain user macro, for example 17
5. Go to Monitoring => Problems and make sure that the problem is created
6. Open event details of the created problem
7. Check "Problem expression" and "Operational data" fields

Result: "Problem expression" and "Operational data" fields contain the value of macro {$TEST} even though it was the {$TEST:regex:"x"} macro that was resolved when creating the problem (33 instead of 15).
Expected:
The context macro should've been resolved in "Operational data" and "Problem expression" fields.

Example: