On the Log Time dialog, under Internal Issues, Tempo should be aware of issue security and not display any issues which the user can't view.
For example, we currently have 7 Internal Issues and they all live in a single Jira project. Right now, we restrict the users who can view that project in the project's permission scheme. However, we have a request from the business that all users be able to log time against one specific Internal issue, but only specific users can log time against the other 6 Internal issues. So I changed the project permissions to allow everyone to view the project, changed the ability to log work permission to allow all users to log work on the issues, and then implemented issue-level security on the 6 issues we want to restrict. But when I login to Jira as a user who should only see the one specific Internal issue, on the Log Time dialog under Internal Issues I see all 7 issues listed and I can log time against any one of them, even though the user can't view 6 of them. So our only current workaround is to create an entire new Jira project just for that one Internal issue that everyone can see and log time against, and leave the other 6 Internal issues in the existing project.
| Tempo Products | Tempo Timesheets |
| Tempo Platform | On-Premise |
We would like to have a slightly more generic approach. Tempo may not show up private worklogs "hidden" by security levels at all!
Since having started with Jira in 2020 we have an enterprise wide "Personal Jira Issues" project with a security scheme allowing private issues for author visibility only. This is a widely used project an anyone knows by now - private issues and worklogs are private, when set to private visibility. Even admins do not have acess to those issues.
Know we made our decision for tempo features last year and had to learn now (!) - it introduces backdoors and worklogs for private issues are not safely private any longer :-(
It is a large loss of trust in Jira - and Jira admins. Anyone hearing about it is astonished and disturbed, that such a basic feature (security levels) is not respected by THE leading plugin for time management in Jira. Basic users do not think in "plugin" level - Jira is our issue black box that have to work.
So we would really appreaceate, if this feature - adressed in 2021 already :-( - may come into live.
Best regards
Markus