Jump to content

Restrict user to add/update time logger


Remus Avram

Recommended Posts

Posted

Hi Remus, this makes sense and there are a few requests for similar features. We have not made any decisions or progress on this matter yet.

The best solution at the moment would be to listen to the timelog changes with an api listeners and warn/revert the change

Posted
5 hours ago, Mattias Lagergren said:

The best solution at the moment would be to listen to the timelog changes with an api listeners and warn/revert the change

Thanks @Mattias Lagergren for the feedback. We will try to do it like this.

But the problem here is that if the production would like to allow only one artist to update his/her time logged, it's not possible.

Posted
17 hours ago, Remus Avram said:

But the problem here is that if the production would like to allow only one artist to update his/her time logged, it's not possible.

Aha, so most artist should not be able to change their timelogs a week after - but one or two artists would be allowed?

Posted

Nobody should be allowed to change the timelogs a week after, but in an exception case, the production would like to allow the specific user to do it. 

Or Production should be allowed to change their timelogs.

Posted

I see, thank you for elaborating.

The best solution at the moment would probably still be an event listener that warns/revert changes. A custom attribute could be set and read on certain users to allow them to modify their timelogs regardless of that limit.

I will update our feature request with details from the use-case you provided.

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...