Please (please, please) allow newlines (line breaks) to be entered in the Event Name field of Triggers.

It's basically a necessity to formatting a legible and helpful monitoring alerts to users.

Imagine if I wrote this whole description without line breaks and included multiple long  all-caps macro names. Add some markdown syntax on top of that so that I can format the message nicely for the destination app. It's a jumbled mess!

As a workaround, I've resorted to encoding newlines as "
n" so that the notification script I use can convert them to proper newlines. This is nice for the users but makes our Event names even worse!

Compare the following real-world example:

What I have to write:

COMPANY User Daily Sum - Difference Between APP1 and APP2: `{ITEM.VALUE}`
n` `
nDifference is calculated using the following SQL:\\n```\\nApp1:\\n{$COMPANY_APP1_USER_DAILY_SUM.SQL}\\nApp2:\\n{$COMPANY_APP2_USER_DAILY_SUM.SQL}\\n```
n[App1 Monitoring Catalogue]({$APP1_MONITORING_CATALOGUE.URL})

What I want to write:

COMPANY User Daily Sum - Difference Between APP1 and APP2: `{ITEM.VALUE}`
` `
Difference is calculated using the following SQL:
```
App1:
{$COMPANY_APP1_USER_DAILY_SUM.SQL}
App2:
{$COMPANY_APP2_USER_DAILY_SUM.SQL}
```
[App1 Monitoring Catalogue]({$APP1_MONITORING_CATALOGUE.URL})

Which one is easier to understand/modify?  

In case someone says: "Use the Description field instead"
I know that I can, but then where do I put comments for myself about why this trigger was requested and how the sometimes-complicated trigger expression works?