Issues vs. Tasks - difference in functionality?

Good to know Skye, Thanks. For the same reason, that wouldn't work for us either. For these particular issues there are a set of tasks for a couple different people (although the issue was only being assigned to one person. As I dug even deeper I found even though the issues were being assigned to this person, the tasks were also beings assigned - sometimes to her, sometimes to someone else, which caused double work to be done. It was a whole hot mess. For us, it would be great if different default planned hours could be assigned to issues based on the custom form or the queue topic. Although I can see where others would want those default hours to be based on something else.

Yep, for me it ended up boiling down to trying to understand the philosophy. So, it seems possible that Workfront doesn't have a good solution for this kind of stuff (default Planned Hours in a request or issue object). When you're specifically talking Resource Planning, and issue objects are defined as "ad hoc" work I see why issue objects are optional and "Planned Hours functionality" apparently has no place in a Resource Planning roadmap. I still kinda want it though. :) -skye

Ran across this and upvoted your link....I was actually looking to see if expenses could be added on Issues....surprised you can't, especially since Issues are so easy to enable for groups to create work. I also agree that the overhead to convert Issues to Tasks is NOT fun...and in the case of some of our users, it creates unnecessary overhead they really don't need when it comes to entering and managing quick one-off requests. However, an automated way to do this would be so much better! :) Admin Kelly-Wehrmann SSFCU