Project Properties: Designate Fields As Required

[#1]

Would it be possible for Admins to designate certain fields in Project properties as required in order for Project Owners to create projects?

Portfolio and Program are very important fields and Project Owners often forget to select them when creating projects. If we could require values in those fields then Project Owners would be forced to make selections when opening projects.

[#2]

I concur to this idea. When a user creates a project without a request, it isn't added to its proper Portfolio. If the user doesn't add a Program Name, then it won't be filed correct - adding issues for users. Having Program Names and Portfolios as required would avoid this issue from happening.

[#3]

To add to this, I want certain fields to be required by certain groups. For example, clients won't know certain fields when submitting a request so they are blank so I can't make them required. But when the intake team/managers review the request, I need them to populate certain fields or reporting doesn't work. They keep forgetting to fill in certain fields.

[#4]

We waste a lot of time each quarter auditing projects in the system where Portfolio and Program are left blank. The ability to make these required would be an immediate time savings for us.

[#5]

Yes! I frequently have to go back and update things like 'company' since it isn't required.

[#6]

Great idea– we'd definitely put this to use!

[#7]

This would be extremely useful as our team uses the Portfolio and Program to tie back to specific reporting elements we've created with custom forms.

[#8]

Hi WorkFront, any thoughts on this? I've seen more than 1 submission regarding this. Really want at least Portfolio to be required!