Tempo Internal Issues is one of Tempo Core features that is available for Timesheets and Planner by Tempo on both the Cloud and Server/DC Data Center platforms. Due to limitations with Jira Cloud, the required permissions for Internal issues are different between Cloud and Server/DCData Center, to managing them varies depending on your business workflow.
Similarities:
Internal issues need to be configured in Tempo Settings > Configuration and require no Remaining Estimate. When issues are configured as Internal in Tempo, they are not considered as billable hours (with Timesheets).
Differences:
Internal Issues on Cloud
Users need to have Browse Project and Work on issues permissions of the Internal project(s).
New UI for the Internal Issues page
/wiki/spaces/HCTIMESHEETSDC/pages/3390244298Data Center
Users need to have Work on issues permission of the project(s).
UI for Internal Issues page is not updated
Here are some more details about the permission differences for Internal issues between the Cloud and Server/DCData Center, which changes how Internal issues are used on each hosting platform:
Permissions for Internal issues are fully granted by Timesheets on Server/DCData Center; on Cloud, the permissions are granted to users with Project permissions (Browse Project and Work on issues). Due to these permission differences, managing the Internal issues' permissions may take more steps on Cloud than on Server/DCData Center.
As a result of the required Project permissions on Cloud, it’s not as easy to share Internal issues with all users when these issues live in different Jira projects, especially if a company has strict standards on controlling what can be seen by whom. This is why it’s recommended to keep all Internal issues in the same Jira project - it’s simpler to manage and allows you to give the necessary Project permissions to all users.
In contrast, on Server/DC Data Center the Browse Project permission for Internal issues is granted by Timesheets, even if Internal issues are in different Jira projects. Users don’t specifically grant the Browse Project permission to view the issues so that they can work on them. Project admins only need to grant the Work on issues permission to all users for the Jira projects that have Internal issues. The advantage of Timesheets giving the Browse Project permission is that users are allowed to view and log time on only the Internal issues, but they are not allowed to see the whole project(s), and it’s easy to manage Internal issues coming from different Jira projects. The disadvantage is that Timesheets bypasses Jira’s permission rules.
Different ways to manage Internal issues based on permission differences on Cloud vs
Server/DCData Center
Using JQL - If you have internal issues coming from different Jira projects, it’s best to group them by JQL and run in Tempo Reports. This is recommended for both Cloud and Server/DCData Center.
Using Jira projects - To keep it simple to manage Project permissions for Internal issues on Cloud, it’s recommended to put them all in a single Jira project. This is also recommended for Server/DC Data Center if Timesheets bypassing Jira’s Browse Project permission does not conform to company policies/standards.
Using Tempo Accounts - Instead of using JQL to maintain the internal issue list manually, linking Tempo Accounts to internal issues lets you easily group/filter them in Tempo Reports for both Cloud and Server/DCData Center.