Several team I work with use "URL hacking" to pre-fill tickets, as a sort of template for tickets that often require fields filled or frequently ask for the same type of information. An example:
{F28599690}
{F28599692}
It would be useful to track when a ticket was made with a special link like this, to see how often it is happening or to find opportunities to direct people to the links. The easiest way I can think of is to use a yellow tag (such as #technical-debt ) along the lines of #ticket-from-template (or some more elegant name). Then the pre-filled tickets-by-URL can simply have that tag and automate the addition.
The risk I see is similar to #epic , wherein a ticket is made with #epic and then subtasks are made without removing the #epic from each subtask (each of which is not likely also an #epic ). In such a case, the ticket would be tagged with #ticket-from-template because it is a child of a task with that tag, but it will not have been made from a template because the auto-tag scenario only occurs when creating a ticket as a child, and the special URL would be inherently avoided.
(It would actually be nice to make a rule that excepts certain tags from tickets created by the "Create Subtask" option, and include #epic and this new tag in that rule, but that is another idea altogether, see {T220835}).