Welcome to Tempo’s Idea Portal! Your suggestions are valuable to us and help us make our products even better.
Below is a list of ideas for Tempo, so please search, review and vote for those that would help you the most. We encourage you to add an idea if you don’t see it listed. You can stay updated on the work we are doing here at Tempo by contributing to this page.
To learn more and see our Frequently Asked Questions, click here.
Second this! I would like to be able to grant permission to log time on issue types to certain roles (ie: only project managers can log time to Epics, everyone else must use Tasks, Stories and Subtasks)
I still think this is very important. A better way is to be enable an administrator (or few) to select the queries that can be used in Timesheets and nothing more. Seems fundamental.
Guest
Workaround :
Using workflow property jira.permission.work.denied worked for us : https://confluence.atlassian.com/jirakb/how-to-restrict-log-work-on-a-specific-status-834225982.html
Copy the workflow that you are using, assign it to the workflow scheme but apply it only to the issue type you want to limit log time.
When done, modify the new workflow, and add the property jira.permission.work.denied on all status.
Time consuming, but it works for now. Major downside is we now have to modify 2 workflow at the same time
+1
+1
+1
+1
We need this in out work process or any workaaround to manage logging avaliability.
We can create, for example, custom javascript code in jira header , but this will be unstable.
We need this!
Second this! I would like to be able to grant permission to log time on issue types to certain roles (ie: only project managers can log time to Epics, everyone else must use Tasks, Stories and Subtasks)
I still think this is very important. A better way is to be enable an administrator (or few) to select the queries that can be used in Timesheets and nothing more. Seems fundamental.