4

Scenario: I'm a director at an IT company who manages implementation specialists. In addition to implementations, these specialists also work tickets for their customers after initial implementation is complete. From my perspective, a project is essentially a bunch of tickets (i.e. cases) and I just want them grouped according to invoice lines (i.e. project tasks). To say it differently, a Field Service work order has a lot of the functionality I want for my projects but Project Service has it grouped the way I want to report it. Meanwhile my resources want a single place that contains their to-do list (i.e. project tasks/tickets). And I want that too because then I can get more accurate reporting on utilization and percent complete roll-ups. To be clear, I know I could create entity relationships between these items to achieve my objective in the short-run but I would prefer to avoid a data migration / kludge solution.

Category: General
STATUS DETAILS
Needs Votes
Ideas Administrator

Thank you for your feedback. Currently this is not in our roadmap, however we are tracking it and if we get more feedback and votes, we may consider it in the future.

Sincerely,
Girish Raja
PM, Microsoft