Request/issues should inherit priority from the template they are converted from

Description - 

It does not seem logical to have a converted request/issue NOT inherit the priority from the template it was converted from, seeing as in almost all cases requests/issues originate from a request queue and are converted to a project using a template (with a priority designated in the template).

Why is this feature important to you - Accuracy of defining priorities and one less step for a project manager to do when converting requests/issues

How would you like the feature to work - request/issue should inherit the priority of the template they are converted from

Current Behaviour - request/issue does not inherit the priority of the template they are converted from