The label "Subject" is confusing for the users who are already typing it in a custom form. I want to be able to rename it to better reflect its purpose.
Thank you for your votes and comments! This functionality is now on our roadmap and planned for 2019. We will share more information as it becomes available during our roadmap calls.
As stated above - lets just get rid of the Subject line all together! I believe it should be an option at least! Actually better yet the system should generate the "subject" as in either take the name of the request queue and give options to add a number sequence, date/time, submitter etc etc...
So many times I've been in a high level meeting and the topic of Subject comes up! And it always ends with -- well that is a stupid requirement and we will need to live with it.
As an update on this, the feedback you have provided on this area in general is being incorporated in a large initiative on heavily improving the intake experience. As it is a large initiative, the ETA goes out of the guidelines set for Idea Exchange Planned ideas, hence we are marking this as Not Planned. However, we will be reaching out proactively during the research phase of the aforementioned initiative for further details and feedback on the topic.
We would like to be able to rename the Subject field for a better user experience as it can be confusing to our requesters. We would also like to prevent special characters from being used in the Subject.
Thank you for the submission! We think this is a good enhancement to the Workfront platform overall and this product area in particular!
Workfront currently prioritizes large-scale, foundational enhancements such as the new Reporting experience and changes to the core data model, so this item does not fit in our near-term roadmap. As such, I am marking this as Declined now, but we'll keep this in our backlog for the improvements for this area so that we can revisit the decision in the future.
