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

We would love to have this feature as well! 😃

Hi everyone, thanks a lot for your continued input! I've added the "Backburner" status here - our Product team is interested in this request and will investigate when they can. I'll get back to you when there's an update. 

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

Agreed, this would help if you want to use custom fields to denote say "bugs" or some type of agile issue type, before the task is created.

Hi guys, any update on the above? 

We are implementing an issue tracking system through request forms, When an issue is resolved, we need to have the QA person to update a few drop down categories, It would be ideal to have a 'required' function or a prompt based on Status change

This feature is very important, when it will be applied?

Hi @Lisa, Any update here? Looks like it's gotten over 100 upvotes on the original post now. Thank you!

I too would like to see an update.  If you want to try to define task types in a team, say if working in software development, such as "bug" or "impediment," it is very useful to insure that the type of task is defined when entered in Wrike.  The only way I can think to do this right now is via a required custom field.

Fingers crossed for movement on this to "in development"!!

Hey everyone! As I mentioned above, our Product team is interested and finds that the idea makes total sense. There are no plans for this in 2019, so I'll be back with an update in Q1 2020. Having said that, please keep your use-cases coming, they really help the team review and plan. 

Have a great day 🙂

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

Lisa

Use Case: Enforce Data Validity

We are starting to do a lot more external reporting on the Wrike data from the BI Export. Since we have no way in Wrike to require custom fields to be filled out, custom fields are very difficult to manage. Our data becomes stale very quickly unless managed very closely.

Implementation Idea:

When a custom field is created or edited, there could be a boolean option for for "Required Field". Once "Required Field" is checked a single select drop-down list would appear showing "Required Field Triggers" = ["On Task Created", "On Status Changed", etc.].

Once a custom field is set to required, a window would popup telling the user "please fill in the missing custom fields" whenever the specified trigger above occurs.

We are excited about this possibility!

Seth Neds Thanks a lot for sharing that! 

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

Our team desperately needs this too.  We have several custom fields, but with no way to make them 'required' they are often left blank - which causes bad data reporting.  We currently use Jira for our developers and would love to migrate them to Wrike so we don't have to manage both tools - but we need to be able to pull stats on things like

- type of tactic (animated banner, static banner, sales rep email, brand-delivered email, flyer, postcard, etc.)

- development company (internal/external - name of agency, etc.)

- delivery method (print / digital / video / etc.)

- campaign ID

I also have need for mandatory fields! But not only for the custom fields, but also for the already existing fields!

Hi,

Voting in favor of having the choice to make some custom fields mandatory.

Thank you

Lisa

This feature would be super helpful. My team's use case is the following: 
If a task has required custom fields, then the user cannot move the task up to the next status in the workflow until they fill the required custom fields. when that happens the user can get a validation error to revisit the task custom fields.

Looking forward to it. 

Thank,
Zak

Hey everyone! Thanks a lot for your use-cases provided here, they're really helpful! I'll be checking with the team in February and I'll get back to you as soon as I have an update!

Thank you 🙂

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

My team would also find mandatory fields very helpful.  I would like to specify at the admin level or at the request form or folder level which fields are mandatory.  For example, if I have 20 custom fields across my Wrike account, there are some that need to be mandatory in X folders (or with X request forms); there is a different subset that needs to be mandatory in Y folders, etc.   The user can't create the task until all mandatory fields are completed. 

The Product team don't have any updates to share at the moment, so I'm leaving the status as is for now. I'd like to thank you for all the use-cases you've provided, I'm passing all of them to the team. Hopefully, it will help get this going at some point! 

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

It is a must have feature for us

Hey Saad F, thank you for the feedback! It's been passed on to our Product team 😊

The idea of mandatory custom fields also helps support and reinforce the business value of wrike analyze.  When working with a large team its very hard to validate all necessary data has been captured which then mitigates the value of the analyze boards if you can not easily ensure all required data has been captured.  Without a feature like this it hinders the business case to invest the time and money into getting and maintaining the analyze tool.

Just an alternative perspective and one that helps reinforce business needs and growth for the analyze add on

Thanks for your input, Spencer Turkot! 

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

I agree, this is a "must have" feature to improve business analysis. 

Our organization would greatly benefit from this as well. We have been encouraging teams to use Wrike Analyze over the past year, but have found limited adoption because the data is inconsistent.  Lisa do you have an update on whether this has been prioritized?

Hey Bertrand Gruyelle and Hanna Rocks, thank you for your feedback here.

While the Product team is interested in this suggestion, there are currently no plans to add this to the short-term roadmap. If there are any updates here, I'll be sure to let you know.

I need to define required fields

Very disappointing to read that this feature isn't in the short-term roadmap. It would be a very welcome feature. I want it to ensure my team are providing complete information on tasks so that I don't have to spend time running 'house keeping' reports and chasing colleagues to complete tasks.

Any feedback on when this will be added to the roadmap would be welcome.

thanks.

Thank you for sharing your feedback here Luke Steggles! I'll let you know when I have an update from the Product team. 

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

Reiterating the need for this in 2021. It would be great that get control over some project inputs utilizing a combination of blueprints with predetermined "required" custom fields. Like many others have said, this cuts down on extra reports and housekeeping if you ensure it's there in the 1st place before moving forward.

Thanks!

Welcome to the Community John Mitchell, and thank you for sharing your feedback and support 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

I would like to add to this thread to bring it back up to view.  Adding the ability to specify a subtask as "required" would be incredibly useful for our particular use case.  Currently, we are manually checking for this and it causes us a reasonable amount of effort.

I've overcome some of these issues by using an exception management approach in a dashboard (e.g. whenever a task is "completed" and a given custom field is empty it appears in the dashboard.

What would be more useful is some highlighting of the custom field when it's not filled out and preventing the task from being completed until there is an entry.