Require Custom/Other Fields with Workflow Rules in Next Gen Project

Question

Not sure if I'm missing something or if this is the expected functionality. As has been stated in this issue (https://jira.atlassian.com/browse/JSWCLOUD-17631), there is not currently support for requiring certain fields in Next Gen projects.

It was suggested to use Workflow Rules and pointed to this article where it says "Remind people to update empty fields" is an option. When I go to the linked article that explains available workflow rules, "remind people to update empty fields" isn't documented there.

Regardless, when I try to create a workflow rule to require a certain field on transition, I'm only shown the attached selection of fields. Is this correct or am I missing something? Is there no way to require fields other than the ones shown here? For example, it's logical that "Time tracking" would be an important field to require, but that doesn't seem to be an option.

John Funk · Answer

Typically, there are only a handful of fields out of the box that support when new functionality rolls out. How they decide which ones, I don't know. I just know it's not there in this case. :-(

unknown · Answer

Is "Time Tracking" considered a custom field? I can't change the name of the field and it seems no different than "Priority" or "Labels" which are optional, but also system provided fields that can be required in a Workflow Rule.

John Funk · Answer

Hi Silas,

Basically, the feature request you cite above mentions that custom fields are not supported yet.

So what you are seeing is system fields that come supported out of the box. That's all you get right now.