Operational Resource Assignments

mah1
Kilo Sage

Xanadu Patch 0

 

We are in the process of evaluating the migration to resource assignments from resource plans and are encountering some issues/questions. These operational assignments are easily identifiable when we use the time sheet portal to log time because the name we used when we created the operational plan appears to be associated with the operational assignment that was created from the migration. 

 

For example, we created an operational plan for Admin and an operational plan for KTLO.  We use a standard naming convention like 2024_Admin_username for operational work type admin and 2024_Support_username for operational work type KTLO. When we migrated those operational plans, the name apparently carried over to the operational assignment.  So, when a user logs time for, say an incident, they see both 2024_Admin_username and 2024_Support_username in the resource plan dropdown. They can easily identify the one to use for support work.

 

But that is not the case when we create a new operational assignment. The only thing we see on the time card is the RA000... number for new operational assignments (i.e., ones that have not been migrated from operational plans). There is no indication if the assignment is for operational work type admin or operational work type KTLO.

 

How can we easily distinguish between the user's operational assignments so we know the correct one is being used?

 

Can we "name" these new operational assignments similar to how we are naming operational plans?

 

The workspaces also just display the RA00... number so it's not clear what they represent.

 

Is there any way to automatically set the operational assignment to the appropriate one by default when the user enters time via the time sheet portal?  For example, set it to the admin one for admin time and the support one for KTLO time.

 

Thank you!

1 REPLY 1

Viper777
Tera Contributor

Well stated.  We are getting ready to transition and this is an issue for us as well.

 

Viper777_0-1734028998964.png

Viper777_1-1734029185939.png