Time tracking on Stories in a Project Agile Phase

[Uncle Rob]

When you log time against project tasks, the time card is categorized as Project / Project Task
When you log time against a story in a project agile phase, the time card is categorized as Task.
(See screenshot below)

Does the category of the time card have any downstream consequences when managing costs for a project?  Or am I overthinking it?  Said another way... in what way does Time Card Category matter?

[Sunil B N]

Hi Robert,

As of now, Project/Project task is a special category which allows to rollup the actual effort and cost to Project and Resource entities.
OOTB, for Project and Project task we categorise to "Project/Project Task" rest all tasks are under the umbrella Task work.
We have seen many customers having multiple custom categories. 

[Uncle Rob]

Thanks Sunil - would you be able to cite a couple use cases for custom time categories?
I'm in that strange place of knowing how it works, but not understanding why its important.

[Jonah Piascik]

Hi @Robert Fedoruk ,

I know this is an older post, but we've been having similar discussions about how our teams can time track against Organizational Project vs. Product Enhancement/Optimization vs. KTLO (Incident/Maintenance).

One aspect of our teams (maybe similar to other Epic Organizations), is our Epic Analysts (and technical teams) provide resourcing for all 3 types of work.

The unified backlog seems to muddy the waters a little bit as well, since our teams are now using Agile and pulling in stories from Incidents and Service Requests (Catalog Tasks) into their sprints, and if they track time at that story level, we are unclear how to determine if that time was spent on supporting a product, enhancing a product, or building out product for a project.