Tempo Timesheets internal issue hide some and show only others

[Deleted user]

I am using jira software server version 8.12.1, and Tempo Timesheets version 10. I have created 5 internal issues. When a jira user wants to record with internal issues he goes to the Tempo Timesheets timesheet (from the my work menu) and clicks on the "+" to create the recording. I would like to make sure that internal issue-1 and internal issue-2 are visible to all jira users in the group jira-software-users, while internal issue-3, -4 and -5 are visible only to a smaller group, called "it users". So I set up a security level permissions scheme with two permission levers: "all" and "it only". In "only it" I have inserted the group "it users". In the other group, I put jira-software-users. What happens is that if I click on the actual internal issues, jira rightly applies the security level and I see or don't see the issue. But if I'm on the time timesheet, from the my work menu, when I click on the "+" to record the hourly work, I see all five issues pop up and this is not good. Am I doing something wrong? Or does Tempo Timesheets itself not provide this type of permission management?

[Angela Nordin · Accepted solution]

@[deleted] new Jira Cloud admin here.  We just purchased Tempo and I am attempting to set up the internal issues permission scheme, without success thus far.  Would you be willing to please share the minimum permissions needed for Jira users to be able to log time in tempo?  What do they need beyond "Work on Issues", "Edit Own Worklogs" and "Delete Own Worklogs"? 

We would like to keep this project and it's issues "hidden" from users except in the Tempo app.  Any assistance you can provide would be very helpful! 

[Mykenna Cepek · Accepted solution]

Sounds like you've just proven that Tempo Timesheets doesn't abide by the Security Level settings for Internal Issues.

I recommend connecting with Tempo Support about it:

https://marketplace.atlassian.com/apps/6572/tempo-timesheets-time-tracking-reports?hosting=cloud&tab=support

These might not be optimal solutions for your use-case, but you could also try experiment with Jira Roles, Jira Projects, or Tempo Permission Roles to separate out access to your various Internal Issues.

Also, different Jira Permission Schemes could vary the "Work on Issues" Tempo Permission (and others) for your different user sets. Just trying to brainstorm other options for you.

[Deleted user]

@Mykenna Cepek thank you for your information, but I am using Tempo Timesheets for jira server, not for the cloud. In any case, if I apply a security level to the issues, if I look at the issues (internal issue) as if they were issues of any jira project, the issues respect the rules that I have set. let's say for example that intenal-1 and internal-2 are seen as jira issues by everyone because that's how the security level "everyone" works. While internal-3 and internal-4 are only seen by "internal users", a jira group that I created on purpose, and have security level "internal" and are only seen by internal users, ok? It's not about jira the problem, but about the page that presents Tempo Timesheets when a user clicks on my work. When you click on my work and you have the calendar view let's say, and you click on the "+" for "log time" then all 4 of my internal issues are shown as a list of internal issues, even though you are a user who should only see the first two. This is my problem. Is there any way, if it exists obviously, to tell Tempo Timesheets "here in my work" if I am user "X" I should only see internal issues 1 and 2 and if I am user "Y" I should see all 4?

[Mykenna Cepek]

Hi @[deleted]. My experience with Tempo Timesheets has been limited to Jira Cloud. If there are some differences with Jira Server, I'm not going to be able to speak to those at all.

In general, though, it sounds like you've got the Issue Security working the way you want it in Jira, but that it's not preventing people from seeing issues as expected in Tempo Timesheets.

That's definitely going to be something to address with the tempo.io folks via their support. I provided that link earlier. Maybe someone else here in the Jira Community will have an idea for you, but your best bet is to connect with Tempo support.

[Deleted user]

time does not have the function I need today. So I solved it by using two different jira projects and working with jira's normal security settings to hide one project from one group and only show the other project to the other group. Patience. In any case thanks for your answers. @Mykenna Cepek