Project Template - Inherit [Priority] from Original Issue

[#1]

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:

1. Workfront user does not have to manually change the project Priority to match.
2. When creating projects, other Project fields inherit values from the original request. Having [Priority] inherit values would lead to a consistent user expectation.

[#2]

YES!!!!!

[#3]

I have upvoted this! In the meantime, I also created a custom report when I forget to check the priority when converting so I can audit my results. Hope this helps you out while we wait for an improvement.

[#4]

Thanks Tracy for the up-vote and the report tip!

We actually made two "whoops" reports - one from the issue angle, and one from the project angle.

We did this because sometimes we have multiple requests resolved by each other (duplicate requests or requests we bundle together, and then later decided to convert to a request).

My image here is a project report, and then we report on its resolvables (the issues). Here we can see multiple issues that'll be resolved by the project.

We had do some text-mode to get it all to work.

FILTER

resolvables:priority=FIELD:priority
resolvables:priority_Mod=cinotcontains

COLUMN: RESOLVABLES

displayname=Resolvables
listdelimiter=<p>
listmethod=nested(resolvables).lists
textmode=true
type=iterate
valuefield=name
valueformat=HTML

COLUMN: RESOLVABLE PRIORITY

displayname=Resolvable Priority
listdelimiter=<p>
listmethod=nested(resolvables).lists
querysort=priority
textmode=true
type=iterate
valuefield=priority
valueformat=HTML

[#5]

Thank you for documenting this. I would like to see this implemented!

[#6]

This looks like it was implemented!!  Woohoo!!

[#7]

Congrats, @VincentGo! It was a good idea and I am happy to see it implemented!