You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
When opening an issue with a 'Time Tracking' entry, if you click on the time tracking entry you get an error message:
"Sorry, you are not allowed to access this page."
With the URL pointing to :
eventum.*****.com/time_tracking.php?ttr_id=undefined
But if you right-click and choose open in new tab/window the URL is generated correctly and it works: http://eventum.*****.com/time_tracking.php?ttr_id=3480
How to reproduce
Open an existing issue that has a time tracking entry.
Click on the URL of the time tracking entry and the pop-up will give the error message:
"Sorry, you are not allowed to access this page."
Possible Solution
Right-click and open on a new tab/window fix it.
Additional context
I tried replicating the issue with the latest Eventum version of 3.8.15(on my test VM) and the same problem occurs.
The text was updated successfully, but these errors were encountered:
Version(s) affected: 3.8.2
PHP Version: PHP 7.1.32-1
Description
When opening an issue with a 'Time Tracking' entry, if you click on the time tracking entry you get an error message:
"Sorry, you are not allowed to access this page."
With the URL pointing to :
eventum.*****.com/time_tracking.php?ttr_id=undefined
But if you right-click and choose open in new tab/window the URL is generated correctly and it works:
http://eventum.*****.com/time_tracking.php?ttr_id=3480
How to reproduce
Open an existing issue that has a time tracking entry.
Click on the URL of the time tracking entry and the pop-up will give the error message:
"Sorry, you are not allowed to access this page."
Possible Solution
Right-click and open on a new tab/window fix it.
Additional context
I tried replicating the issue with the latest Eventum version of 3.8.15(on my test VM) and the same problem occurs.
The text was updated successfully, but these errors were encountered: