I'm not sure why this list of useable variables should be limited in the first place.

+1 super useful if canned responses can use data like

• issue properties -> {issue.propertyX}
• organization properties -> {issue.Organizations.detailY}
• customer properties

+1 this would be very useful for when we want to manually tag someone (e.g. a line manager) with a canned response and not via automation (in the situations where it cannot be automated)

I'd like to use smart values including those for custom fields in a canned response so that I can use all the fields available in my issue, in the comment message. 

Bonus points if I can also use simble math formulas. This means I can have team members quote jobs on the fly by just using a Canned Response.

I'd like to even be able to use Components. It's not a custom field, but it's not on the [List of variables|http://example.com|https://support.atlassian.com/jira-service-management-cloud/docs/create-a-canned-response/]. Component is used in our org to identify which tool(s) the customer is asking about. 

We'd use this for text like "Just checking in on our conversation about TOOL_NAME." 

Atlassian Support steered me to this issue.  I simply want to be able to use the first name for people, as referring to people by their first name sounds much more friendly in a Canned Response than having to use their full name.  

It's much more personable to say "Hi Jerry, just want to let you know we're working on your issue. Bill" than to say "Hi Jerry Smith, just wanted you to know we're working on your issue. Bill Stone".