Ability to submit tasks in a request queue, not just issues

[#1]

This one is the bane of my existence as a creative traffic manager. I understand that submitting issues is legacy core coding from when Workfront was created as IT software before marketing project management was added, but Issues are absolutely meaningless to marketing teams. Converting them to tasks just means there's a massive loss of functionality and history on every submission.

[#2]

As a creative services manager I have to second this and would be most helpful.

[#3]

in user support I also agree

[#4]

I would agree, my creative teams ask me this all the time.

[#5]

This would be the most time-saving change you could make for our users. Because all of our projects are managed by our video production, social media and creative services teams our projects all need to be organized with a parent/child structure. Between the three departments we can average up to 30 new requests per day - even more during peak season. The amount of time that could be saved if the project managers simply had to move and assign the task instead of needing to convert it would be life-changing for us. It would also eliminate confusion on the end of requestors who don't understand (or care about) the difference between a task and and issue. They just know that they asked for something and want to know where to find it.