AFAIK only when your session is 'ended' (logout, inactivity etc)
The issue stays the same, on login you need to fill the non-persistant entity with data, since it will be empty on log-in. So the 'Outstandig issues' need to be persistant, since this has data that need to be commited. the workload objects COULD be non-persistant if created on the spot, but personally I'd make those persistant too in case of logging / reporting.
Maybe I'm not sure how your app is functioning though. Which entity is non-persistant in your example?