We have a mismatch between the [Priority] field values when creating a project from an issue using a template.
Use case: We have an issue with a high priority. When we convert it to a project, the new project has a medium priority. We want the project to reflect the original project's priority.
The cause: The Project Template requires a [Priority] value. All projects created using that template will have that value, regardless of the original request's priority.
Proposal: When creating projects using a template, the new project inherits the [Priority] value from the original request. (Or have the ability to leave the Template value blank, so people who want items with that template to always have the same priority can have that option too)
Benefits:
- Workfront user does not have to manually change the project Priority to match.
- When creating projects, other Project fields inherit values from the original request. Having [Priority] inherit values would lead to a consistent user expectation.
![](https://support.workfront.com/hc/user_images/P98ntkd17wHeSXaG88PauA.png)
![](https://support.workfront.com/hc/user_images/c-ZH6LnkktJOHP0rLiA-CQ.png)