Removing the Subject field from the Request form

Hi Vazgen, Just to make sure it isn't lost in the shuffle - I think there is another concern about changes being made to our production instances without notice. If it were accessible in Preview and scheduled I would feel different, but as we may have our own training guidance and user interaction going on - this causes me concern. I think this is a far bigger problem than just whether or not this specific change is seen as a problem to a random survey of Community users' instance populations. Mark Lopez Centene Corporation

I like this idea as well.

I would rather be able to customize this field name myself, by queue, if possible. We have a meetings team that want this to be called "Meeting Name", we have a request team that wants this to be called "Request Name", etc. Haven't seen any concerns with just "Name" yet but I personally just don't like it because it sounds like the person's name. That's what I would think upon seeing it if I had never filled out a request before. Angie Simon CUNA Mutual Group

I get that the nomenclature within Workfront is to call everything "Name" but people who make Requests are quite often not Workfront users, so that nomenclature doesn't mean anything to them. It's fine for power users who are creating reports and filters, but for requesters, they are never exposed to those naming conventions. This is going to cause chaos for the people who have to action the requests and figure out what the request is and name each one. They already name things badly ("Send me 4 photos for an event" type of thing) but usually there is a big clue in the request name that comes in. Every form you ever fill out in life, from elementary school on, asks for Name, Address, Phone, Email. This is going to throw them for a big loop, especially because there we don't ask them to write in their name with their request, as it is auto-populated inside the Issue.

Hi Vazgen, Please don't fix it by making new problems! I do not want an auto-populated field that my team would have to deal with. Please just allow the user to rename/change the field to suit their needs. If the user wants an auto-populated the subject line field then allow the user to change it, if they want it to say "Project Name" instead of "Subject Line" then allow that. Aileen Aileen Taylor Cell Signaling Technology

I've been following along on this thread, not realizing it was going into Production so soon. I just sent a note to all my PMs asking them to keep me updated on what they are seeing coming in on new requests. My guess is that our regular users who submit all the time, will fill in that field as they normally do without even noticing the new field name. Our infrequent users (and we have a good number of them) who already need a lot of hand-holding though, will likely put their own name in there.

Thanks everyone for the feedback and letting me know the results of the change! The outcome we want to drive is to increase clarity for what the field means, not make it more confusing to people. I want to ask all thread participants to let me know how users respond to the change - do all have the same problem as Denise mentioned? @Denise Moore , how widespread is it at this point? We can make the change fast, I want to ensure we are changing it to the best possible option though. On this note I wanted to ask will be the best label to use for this? Several of you have suggested Request Name as a suitable option. @William English also suggested the word "Title". I have built out a form with several label choices, can you please vote for the most clear ones? "https://forms.gle/wsDi6P2iv1H7ww4t8" Survey Link Thanks, Vazgen Babayan Product Manager Workfront

Yes. Ugh. Sounds ridiculous I know...but, they are putting in their name...or the name of the person who is going to be the contact. Some even name and phone number. Some even the name of the person they think the request is going to. Ugh. If we cannot control our own verbiage and if subject is a problem for some, but some sort of "name" would be better for those people, then wouldn't it make more sense to be something like "request/issue name" as that is what is being filled out...a request/issue. Denise Moore Ameritas Life Insurance Corp

hey @Denise Moore can you be more specific about what the problems are? Is it that requests are starting to come in with the user's name in the request title? Or some other problem? -skye

Oh my gosh...the sudden changing of the Subject field title to Name is causing us HUGE problems. Please tell me that it is being changed back or a better solution is coming VERY SOON!! Or am I missing a way that we get to choose the terminology for our own instance? Denise Moore Ameritas Life Insurance Corp