This artical is for Cloud
Problem:
After updating Time Tracker to the latest version, it automatically moves to the Forge system, which may cause users to encounter Hash 1V47HZL errors. This happens because the Forge system uses a new URL, while the browser cache still redirects to the old URL.
-
Old URL:
/plugins/servlet/ac/jira-timesheet-plugin/timereports-system -
New URL:
/jira/apps/d95630c7-9fd4-495d-8988-b55637f4f8e9/1e298677-4dfa-4966-9486-544a5b279ca7
Solution:
You can resolve this in one of two ways:
-
Clear your browser cache completely to register the new URL.
-
Access Time Tracker directly using the new URL, which will automatically register it:
{JIRA_INSTANCE}.atlassian.net/jira/apps/d95630c7-9fd4-495d-8988-b55637f4f8e9/1e298677-4dfa-4966-9486-544a5b279ca7
After doing either of these, the page should load normally without the Hash error.
Aftermath:
You may encounter an Authentication Error because the previous configuration didn’t carry over to the new Forge system.
To resolve this:
-
Go to the sidebar → Apps in Jira.
-
Highlight Time Tracker and click the … menu.
-
Select App settings.
-
Add your admin group to the Auditors Groups field.
This should restore proper access and resolve the authentication issue.