Removing the Subject field from the Request form

I recommended the same general concept Vic described - provide the same functionality as we have when creating calendar labels, using the variables of our own choosing; and customized on a per queue basis. That sounds like it's beyond the scope of what Workfront is able to invest in this feature request, due to some conflicting priorities. In that case, I would much prefer just being able to define my own alias for "Subject" in the Queue Setup tab. The other auto-naming options suggested don't have much value for our setup. William English T-Mobile

Ditto. We'd have the same issue as Polly and Brandon. Also, agree with the ability to either rename the field, hide it or replace it with our custom field. Vics idea is intriguing. Our Requests go to our most finicky, aggressively critical team members which in turn would impact on using the Request feature at all. Forgo the Request feature and it significantly reduces the Workfront value to our department which I'd really hate to see happen just as I'm about to onboard this department. Tammie Bouchard National Safety Council

Thank you @Vazgen Babayan for posting this here outside Ideas and for providing the survey link for feedback! Tammie Bouchard National Safety Council

I was originally excited for this but after really thinking about it, we would have the rename every single request that comes in. We have so many request categories, and get a lot of requests for each, and would not be able to tell them apart. We'd find ourselves in a situation similar to Brandon with hundreds of items that say "Web Graphic from Julia". If we can't rename it, we'd rather leave it as it is. Our users have gotten used to it at this point. Barb Pilarski Pittsburgh Penguins

I think changing the name of the field to something like 'Request Name' would be helpful and more indicative of what it represents. For both subject and description, admins should have the option to hide them or make them not required. I don't think WF should remove them. I agree with the points made in this thread about the issues autogenerating a request name could cause. A number or the portfolio name doesn't give me any indication what the request is about without having to dig through the custom form and wouldn't differentiate enough from all the other requests for the same portfolio (or whatever the autogenerated naming convention is). We only use one request queue- in which our users can request multiple related deliverables from a single request form. I then create a project for each deliverable (video, web, social, etc) by copying the first project I create and renaming it to easily identify which deliverable the project is for. So it's unclear how linking the field to a custom form field would work for us since often times the request is for more than one thing. We haven't had issues using the subject field. If changes are made to how the subject line works, I would need to be able to configure it myself for our instance (without limitations set by WF that would render it not useful). But even so, it could present some issues and I would definitely need the option to turn it off. Janelle Hicks Lifespan Corporation

Hi everyone, Thanks for all the feedback and votes! As a result of this, we will rename the Subject field to Name for a short-term solution and will continue research for the long-term solution of defining your own naming convention using custom field information. Thanks again! Vazgen Babayan Product Manager Workfront

Why do I have visions of users entering their own name on every request....? Barb Pilarski Pittsburgh Penguins

I came here to say the same thing as Barb: users are going to enter their own name on every request. Sorry for any misunderstanding you got from my survey answer: it was never my intent to indicate that "Name" was a satisfactory title for the request. -skye

Yep - I agree with Barb and Skye. Users are just going to enter their own name in this field now. Satchell Mische-Richter Quality Bicycle Products

I laughed out loud when I got @Barb Pilarski 's message :) How true. Anyway, could the fix be as simple as calling that field 'Project Name'? I know that would fix it for my organization. Just a thought, @Vazgen Babayan ! Brandon Hamm Bravo Group