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.
We would like to give our staff some guidance in plain sight in which projects they need to plan and/or track time. It is a compliance issue in our case. Staff associations are powerfull in Germany by law. They can prevent us from using Tempo altogehter if we do not comply.
Some projects our staff works on are in a customer context. Others are not. They only need to plan and track time for projects where customers are involved.
So in both cases it is the same staff members. So the need Timesheets and Planner access.
Out of 14 offices in our organization, only two have opted to use tempo for internal time tracking and ressource planning. For the rest, the extra screen real estate used on cases where Tempo is not needed is VERY annoying. We may eventually have to honour the annoyance of the many over the needs of the few.
In our company, we also need to set up the plugin project-specifically, since it is not required for all projects (e.g. portfolio projects do not need time tracking).
Is there already a function to deactivate the add-on in the screen mask and in the project sidebar or to set it to invisible?
We would also very much like this feature. In our use-case we have multiple Product Teams, some of which need to track their hours, some which don't.
In order to not foul up the interface / screen real-estate, having this disabled per project would be great!
In our case: we would like to enable it per project category, but having a toggle to enable/disable per project would be great already! (see for Checklist Pro for an implementation example).
We currently support managing access to Tempo products on a per user basis using Global Jira Permissions. That way it is possible to specify exactly who has access to Tempo.
I realise that our current solution may not satisfy the need being expressed here, but I'm curious to understand this use case a bit better. In what circumstances would you like to hide Tempo on a per project basis? Is it to prevent time being tracked against selected projects, or is it more that certain users do not need to track time?
Andrew Ramsay
We would like to give our staff some guidance in plain sight in which projects they need to plan and/or track time. It is a compliance issue in our case. Staff associations are powerfull in Germany by law. They can prevent us from using Tempo altogehter if we do not comply.
Some projects our staff works on are in a customer context. Others are not. They only need to plan and track time for projects where customers are involved.
So in both cases it is the same staff members. So the need Timesheets and Planner access.
Attachments Open full size
Out of 14 offices in our organization, only two have opted to use tempo for internal time tracking and ressource planning. For the rest, the extra screen real estate used on cases where Tempo is not needed is VERY annoying. We may eventually have to honour the annoyance of the many over the needs of the few.
Look to Risk Register (https://marketplace.atlassian.com/apps/1213146/) or Multiple Checklists (https://marketplace.atlassian.com/apps/1220026) for elegant solutions on how to implement this.
Attachments Open full size
Dear Tempo Team,
In our company, we also need to set up the plugin project-specifically, since it is not required for all projects (e.g. portfolio projects do not need time tracking).
Is there already a function to deactivate the add-on in the screen mask and in the project sidebar or to set it to invisible?
Kind regards from Germany
Christian
Attachments Open full size
Hey Tempo,
We would also very much like this feature. In our use-case we have multiple Product Teams, some of which need to track their hours, some which don't.
In order to not foul up the interface / screen real-estate, having this disabled per project would be great!
In our case: we would like to enable it per project category, but having a toggle to enable/disable per project would be great already! (see for Checklist Pro for an implementation example).
Cheers,
Robin
Attachments Open full size
updates?
Attachments Open full size
Any ideas that?
Attachments Open full size
There are workarounds that hide the "log work" section, but in it's place you end up with a "Plan Time" section Which is also not wanted.
Attachments Open full size
Would also like this feature.
Attachments Open full size
Our customer do not want to see any tempo panel on issue screen. We need to remove then from certain project
Attachments Open full size
We currently support managing access to Tempo products on a per user basis using Global Jira Permissions. That way it is possible to specify exactly who has access to Tempo.
I realise that our current solution may not satisfy the need being expressed here, but I'm curious to understand this use case a bit better. In what circumstances would you like to hide Tempo on a per project basis? Is it to prevent time being tracked against selected projects, or is it more that certain users do not need to track time?
Thanks for the feedback!
Hlynur Johnsen
Group Product Manager - Tempo for Jira
Attachments Open full size