Skip to main content
Level 6
May 23, 2019
Question

Removing the Subject field from the Request form

  • May 23, 2019
  • 76 replies
  • 10118 views
Hey everyone, >Renaming the Subject field on the request form is currently one of the top-voted items for the Idea Exchange. We are currently debating an option to automatically generate incoming request names using a predefined naming convention and remove the Subject field from the request form altogether. There are several options we're thinking of for the naming convention, so your feedback will be invaluable for us to understand whether we are close with our hypothesis or completely off track. If you could please fill up the form below, that would help us immensely!

76 replies

Level 9
June 19, 2019
I think the Subject Field should be an option under NEW ISSUE FIELDS under queue setup. You have name of project that tells you type of request and then queue topics to help narrow down topic. If detailed info is needed it can be added within custom form. Thanks. Susan
Level 4
June 19, 2019
Agreed! "Name" is a very misleading label for this; it would be better to revert to "Subject" while working on an option to make it customizable. Linnie Ciepielowski Esri
Level 8
June 19, 2019
@Vazgen Babayan I like this idea.. ^ Dustin Martin Assigned Support Engineer Workfront
TamBou
Level 5
June 19, 2019
This would be prefered as long as we can still customize the 'layout' of the form. Tammie Bouchard National Safety Council
Level 3
June 19, 2019
Same here I am afraid. Changing Subject to Name just doesn't make sense. That is really confusing my users. Marta Sowa Sky Betting and Gaming
New Participant
June 19, 2019
We've also seen a number of requests come in with the requester's name in that field. I opened a ticket with support and this is what they had to say: This change was made from Subject to Name to provide consistency with the rest of the system, specifically New Project screen when creating projects from the template. I would recommend adding your complaint if this causes confusion for your users in our community. Currently it is not customizable. I will be closing this ticket now, but let me know if you have any questions. I'm assuming this post is the first step to getting this ridiculous nomenclature changed. Good luck to all! Steve Werner CentraState Healthcare System Freehold, NJ
Level 5
June 19, 2019
Lol! This explains why I've been seeing a bunch more requests with the requestor's name as the title. Vincent Goodwin The Capital Group Companies
BrandonNW
Level 6
June 19, 2019
To piggy back on Kevin Quosig's suggestion, can we not just add customization to this field name? That way every organization could name it whatever they wanted. Brandon Pritchard System Administrator iNHouse Marketing - Nationwide pritcb1@nationwide.com
Level 6
June 19, 2019
Vazgen - as you know I am a huge supporter of the "Subject' change ;-) -- Just not this way, especially with no communication. A few of our more seasoned groups have user guides that call out Subject. And as many have hinted at above... many user's have entered their name. and not to pile onto this topic - BUT I will ;-) in our areas many users have been stressing out over this change, so it will be "nice" to see it revert back. BUT some harm has been done with this quick change - in that now other teams are asking or telling me: oh I thought this field couldn't be changed -- but now it is and we want it to say XXXX. Or as many have said here (and I voiced during our leap chat) it would be great to grab meta data from the queue topics and maybe even a custom field from the form -- but in general make it very custom as its an important field. So how far along is your team on a new Request system/page/form/look and feel? okay 'vent mode' off :-) John Seitz DTCI | Disney | ESPN
MoniqueEvans
New Participant
June 19, 2019
We haven't run into this issue yet but I definitely see it coming, since some people were already putting their name in the field before the renaming. Monique Evans Stanley Black & Decker, Inc.