Michal,

For the users that aren’t reporting time, do you really need the associated resource. The system supports having users that are not resources as well, resources who are not users and users who are resources. Do you need to see capacity or plan work for these non-time reports? If no, hen I’d end date the resource and they’ll no longer be chased for timesheets.

If you need the resource, because they are occasional time reporters, them one of the auto timesheet options will help, of which there are two automatic timesheet options:

1. Zero Hours - this will, for any resources in a selected resource portfolio, create a zero hours timesheet for resources without any planned work (Allocations/Standard Activities).This supports the “occasional” resource who needs to report time if/when they do it.
2. Automatic Timesheets based on planned Allocations and Standard Activities. 

Hi Malcolm ​@mlea ,

As I mentioned in my post, we are indeed considering enabling automatic timesheets for non-timesheet users. Due to reporting needs and tracking where a given user is planned, every user account is linked to a resource record. For this reason, we can’t simply opt out of this setup.

So my question would be if you plan to have any option, even a custom one, to configure timesheet notifications based on roles?
Thanks

I know notifications are on the backlog for a major overhaul. 

Suggest you add this to the Enhancement list:

https://success.planview.com/Release_Information/Planview_Enterprise_One_Product_Releases_(Version_15_to_October_2022)/Planview_Enterprise_One_New_Release_Explorer/Planview_Portfolios_and_EA_Enhancement_Campaigns

​@mserafinowski we too have resources that do not track time in the system. This is so we can create reports showing all personnel at the company for workforce planning, and see who reports to who.  We do this by having a resource status that is Active, no time reporting. This helps filter those out of portfolios or reports as needed.  We also put a start & finish date (either the date they quit being required to track time due to a promotion, or equal to the start date) on the resource.  Having the finish date tells Planview logic that they are no longer reporting effort and therefore would not show up on delinquent timesheet reports nor notification tiles.  Maybe a solution for you to?

Note: the resource status in Planview does not drive anything that we have found, thus the need to also have the employment end date.  They are still a current personnel member until we set the resource status to Separated.

Hi ​@pamela.sargent,

Thanks a lot! That sounds like a great idea. Unfortunately, we have resources planned against different projects or ongoing activities where timesheet submission isn’t required. This is due to our organizational structure, reporting purposes, and varying levels of seniority.

We can implement a similar approach but only for those who never submit timesheets and aren’t planned against any projects/run activities. Having automated timesheets seems like the most reasonable option, though I’m not the biggest fan of this workaround as it will create additional and unnecessary records in the database.

I really wish we had a basic mechanism to control who receives which notifications. The simplest solution would be to base it on user roles but it seems we’ll need to wait for Planview to develop this functionality.

I found an enhancement request for a very similar idea. If anyone would like to vote for it, please feel free to do so:

https://e1.spigit.com/e1prmcontinuous/Page/ViewIdea?ideaid=7470

​@mserafinowski - Just FYI: just because a resource has an end date does not stop anyone from creating a resource assignment against them. So if planning needs to occur but that effort does not need to be accounted for as actuals, aka a timesheet is not needed, then you could do reserves against them so that the effort expires but you can still see the demand against the resource.  When an assignment is made a pop-up displays saying the dates are outside of the employment dates but it does not stop you from creating the assignment.  Just don’t do allocations unless you change the progression option to expire vs honor finish dates, which can’t be done at the assignment level but at the activity level as a whole. 

​@pamela.sargent, thanks! 
We know that we can create an assignment even if a resource has an end date. However, we have resource integration, and if there is an end date, the resource is moved to the archive... We don’t even want to think about the effort and costs associated with rebuilding this entire configuration. That’s why we are so eager to have the option to set email notifications for roles.