Great -- glad we are on the same page. You should be looking for Name -- not Subject.  

@MelanieM1  --  Where you said, "if the user enters their Program Name or Project Name in the subject field, it would be nice to have that automatically applied to our custom field." -- create the native field, set the reference as "Name" and the label as "Program Name or Project Name" and put it in...

I've tested this in my instance, and if you recreate your custom field as a native field tied to the request name, the request Subject line does copy into it.

I think if I was going to do this, I'd explore using Fusion to place it as a note on the hours entry. 

it's a recent bug, go ahead and submit a case to Support.

I think potentially, since your end goal is a CHART, calculated fields would be the better option for you to go in. Grouping text mode is not going to result in a chart at all. Please refer to the API explorer's reference tabs in order to get what you need for calculated field expressions. In brief:...

For this you would be starting off with an issue report and grouping by the different levels of topic groups. Similar concept, but a bit more difficult, and also produces unwanted results if all your queues have different numbers of levels.   You might find better value out of reporting on the reque...

It's quite possible that the reason the Task Details overview doesn't show assignee information, is because it's right there in the upper right corner of that page. All you have to do is click on the circles and it will show you the full list.   To answer your question/s though, probably {assignedTo...

if you need that level of specificity, probably best to start with a queue topic report. Each level of topic group would then be its own column. And you would make as many columns as we need.

Can you just change their account password and leave it active? Otherwise yes. Calendars, automations, reports that are "running as" that user.