[Status: Backburner ⌛️] Set "Required" custom fields

Currently a user can create a custom field for their projects and tasks. 

 

It would help if, there was a way to set these custom fields as required.

And, if the problem is because the fields are specific to the user, then I would like the ability to make custom global fields that are required.

It's the missing ingredient in custom fields. They're useful for one person. but human nature means they might not get filled out, unless forced.

Maybe there's already a way, or already a suggestion for this

Upvote 194
80 comentários
Spot On Innovative Approach Stellar Advice
Avatar
Hello Shaun Carlson, thank you for sharing your use case and current practices here. I've passed on your feedback to our Product team.
 
If there are any updates in relation to this in the future, we'll be sure to let you know 🙋🏻‍♀️

Cansu Community Team at Wrike Wrike Product Manager Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

Cansu Wrike Team member Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

0
Ações de comentário Permalink
Spot On Innovative Approach Stellar Advice
Avatar

I agree, this is a must and would be so helpful to be able to force some fields to be filled before closing a task.

0
Ações de comentário Permalink
Spot On Innovative Approach Stellar Advice
Avatar
0
Ações de comentário Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Need this feature! 

0
Ações de comentário Permalink
Spot On Innovative Approach Stellar Advice
Avatar
0
Ações de comentário Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Yes please do the required fields!!!

0
Ações de comentário Permalink
Spot On Innovative Approach Stellar Advice
Avatar
0
Ações de comentário Permalink
Spot On Innovative Approach Stellar Advice
Avatar

 

😡

I would assume the main reason for custom fields is data segmentation for analytics. Without the field being mandatory results in very poor BI. I see Wrike analyser now shows tasks as "N/A" when data has not been entered but this is still an issue with external BI solutions. When using the API or the WDC you get a null. Example you have 200 active tasks, a custom field for company (100 with company x, 20 company y, 5 company z & 35 with no value set). The total active tasks will result in 200 but when you create a widget/dashboard on the custom field company it will only show 125. I have a consultant creating a DW to create a flat table ensuring every tasks gets a value for a custom field i.e. "None" for the ones that have not entry. This then ensure we get the right total of tasks but still does not mean we have the right info, only a whole lot of tasks set to "None".  

This request seems to be 3 years old with status "Backburner", with no indication on when / if a resolve will be in place. So question remains "When will you be able to make custom fields in a task mandatory" 

 

1
Ações de comentário Permalink
Spot On Innovative Approach Stellar Advice
Avatar

We need this feature too... Another option would be to include who make the update for a given task/project/folder within the API response payload. That way you have several options to let that user know that additional information is needed.

0
Ações de comentário Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Thanks a lot for your detailed feedback here Stephen Fish! And thanks for supporting here as well Guillermo Guinto

I understand that you're disappointed by the fact that for now the suggestion isn't planned for implementation. Our Product team would love to be able to implement most of the Community suggestions, but they have to prioritize over multiple factors and sources of feedback.

I'll make sure to continue to flag your feedback here with the team and I will let you know if I get an update in relation to this suggestion. 

Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Lisa Wrike Team member Become a Wrike expert with Wrike Discover

0
Ações de comentário Permalink
Spot On Innovative Approach Stellar Advice
Avatar

This would be very helpful for our team. There are specific fields we need for reporting purposes. At the moment we have created Blueprints and require everyone to enter projects and tasks through a request form to ensure the requirements are met, but we often have the rouge team members that try to enter a task manually so we end up with missing fields, then I have to create a report to see all the missing fields and track down the individuals to update them. 

The other thing I think would be great is if the timelog categories could also be required. Same as I stated above, people often forget this step when they are quickly entering time. Entering time is already a pain point for most, but then asking them to go back and update a field is an even bigger pain point. 

A switch to make required or not would be very helpful.

0
Ações de comentário Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hello Kerry-Ann Wilkins, thank you for sharing your feedback and use case here. I've passed it on to our Product team 👍🏼

Cansu Community Team at Wrike Wrike Product Manager Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

Cansu Wrike Team member Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

0
Ações de comentário Permalink
Spot On Innovative Approach Stellar Advice
Avatar

This would tremendously help with our auditing throughout the year.  We need to keep track of partner/sponsor inclusion within our video projects and it's best to verify this information once the project has been delivered/completed.  So requiring certain custom fields to be populated upon marking to 'Completed' is a great way to have a final check on project/task meta data.  Added my vote to this request!

1
Ações de comentário Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Thanks for supporting this suggestion and sharing your use case with us Mike H 🙌🏼

Cansu Community Team at Wrike Wrike Product Manager Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

Cansu Wrike Team member Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

0
Ações de comentário Permalink
Spot On Innovative Approach Stellar Advice
Avatar

We are considering moving to another tool because of the lack of this feature. To keep others from leaving, you should implement this feature. Request forms only help with work intake. However, there needs to be a way to require certain fields. One way could be to add it to the "manage custom fields menu" and have a toggle for each field for required or not required.

0
Ações de comentário Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Thank you for sharing your supporting suggestion here, Seth Neds! Could you please share the reason for your team to want required fields - is it because team members forget to fill them out? If it is so, I would suggest taking a look at the newly released (in Labs) Work Templates. You can create work items and set up which system and custom fields are visible on task and project templates. That way, when there aren't too many fields to fill out, but only the necessary ones, it might be easier to not forget to fill them out. 

Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Lisa Wrike Team member Become a Wrike expert with Wrike Discover

0
Ações de comentário Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Lisa Thank you for the response.

Templates and Blueprints have been helpful for work intake but do not help when something needs to be created, or changed within Wrike. There are many cases when we don't use the request forms. (e.g. when our developers are estimating work and filling in the custom fields.)

Value for us for requiring custom fields:

  • Accurate data for reporting.
  • Governance on the standards we set surrounding custom fields.
  • Ability to standardize required custom fields across hundreds of users. Checking and monitoring fields manually is not practical.
2
Ações de comentário Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Thank you for your detailed reply, Seth Neds! I'm checking with the team now and I'll let you know if there's an update for this suggestion 👍

Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Lisa Wrike Team member Become a Wrike expert with Wrike Discover

0
Ações de comentário Permalink
Spot On Innovative Approach Stellar Advice
Avatar

I really would love to have the ability to make custom fields mandatory

1
Ações de comentário Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hi Beth Christie, welcome to the Community 👋 Thanks a lot for supporting this idea! Please make sure to upvote the original post above if you haven't yet - the number of votes helps the team understand how popular the suggestion is. Here's more detail on that, but please let me know if you have any questions! It would also be great if you could share how you'd like to use mandatory custom fields.
If you'd like to know what this Community has to offer, please check out our New to Community forum 🤗

Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Lisa Wrike Team member Become a Wrike expert with Wrike Discover

0
Ações de comentário Permalink

Folllowing List for Post: [Status: Backburner ⌛️] Set "Required" custom fields
[this list is visible for admins and agents only]

Alto
Didn’t find what you were looking for? Write new post