Pull Users into Custom Forms

Very glad this has been implemented, however it would be AMAZING if we could add multiple users instead of one per field.

This enhancement is now available to all customers! You can find the release documentation and short demo video here https://experience.workfront.com/s/article/2019-3-Release-Activity-Overview-1993224231.

I am leaving the status of this idea as "Planned" until we deliver the other objects beyond being able to link to Users. Look for that update in the near future.

I'm excited to announce that we are close to getting this feature out to you! Coming to Preview on Thursday, May 30th and Production on Thursday, June 13th, users will be able to create a new type of custom field that is a Typeahead field and lets them type and select names of Users that exist in their system. You can find the release documentation and short demo video here https://experience.workfront.com/s/article/2019-3-Release-Activity-Overview-1993224231. The documentation and demo video will be updated approximately 1 day before the Preview release.

**EMEA Exception: Any customers who are hosted in our EMEA data center (CL04) will receive these updates after Leap London.

Josh Hardman

Product Manager, Workfront

Great news, we are starting to look into this. It is our goal to have this available within the next few months. I will keep this post updated as we make progress.

Adding another comment to how useful this would be.

We were doing something similar in SharePoint before coming over to WorkFront. It was extremely helpful in reporting on a breakdown for our initiatives and not having it in WorkFront is a bit of a disappointment, though we will work with it until it can be implemented.

Hey Gevorg,

Thanks for the follow up! That seems reasonable, and I am glad to hear clarity on what the status means. I appreciate the quick response.

Cheers,

-Justin

Hi Justin,

Thanks for the comment and for following up the idea!

As I mentioned in the response, we are really interested in the idea and would love to implement it in future, so it is surely not cancelled, what "Not Planned" means is that we, unfortunately, won't be able to deliver it in the upcoming 12 months, but it will definitely be considered afterwards.

I'm definitely sad to see this marked as "not planned" with so many upvotes. Does "Not Planned" status mean it will be in queue until it does get planned or that it's basically cancelled?

Thanks a lot for the great idea and we highly appreciate your input in making our product better! This looks like very promising product enhancement and we will definitely consider it in future. Unfortunately, for right now, I’m marking this as “Not Planned”, as we won’t be able to deliver this functionality in the coming 12 months. At the same time, please continue adding your use cases to this topic, so that we can take those into consideration when validating the solution.

This would be incredibly useful - if I was building this would add it as a new field type that you can choose when adding fields on a custom field (a lookup) - it would physically store an ID but show the default decode field (eg like project owner stored as a user ID but shows the name of the owner on the project, portfolio, approval etc).

In reporting would then expect to be able to go through the object to its detail (eg project:DE:NewUserField:Name) to access any of the individual items from the object that is linked.