Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Hiding Tempo Plugin on default issue screen

Is it possible to hide the tempo plugin section on a issue?

6 answers

1 accepted

2 votes
Answer accepted

This is a global configuration and will affect all issues. Please have in mind that the Tempo section in an Issue only shows the hours logged by yourself, it does not display hour logged by other users.

I wanted to ask again about if and when this might be changed to be configurable by project.  We have only a few projects that want this section and the other project admins are adamant about not having tempo showing up on their projects at all.  Has this been worked on or can it be added soon?  I'd hate to have to remove the plugin completely over this.  

Like # people like this

Please check below, we found a solution to this using Matthew Beda's approach using ScriptRunner.


you can hide the Tempo section in the issue by disabling a module.

You need to go to Administration-> Add-ons, Manage Add-ons. Expand Tempo Timesheets and click the + next to the modules enabled. This opens the list of modules. Disable the "tempo-worklogs-module" and the Tempo section of the Issue will be hidden.

Kind regards

Susanne (Tempo)

Thx Susanne!

Is there a possibility to configure it for each project or is this configuration always general?

Cheers, Joscha

I need this too. Tempo is installed for a specific team but it's affecting all users now.

Hi Susanne, do you have any info to share on this?


Thank you,


Does not seem to be possible, I get "Module cannot be modified" (Using JIRA in the cloud)

Update: We have had customers reporting that disabling the Tempo panel may cause performance degradation in some browsers.

I would like to add to this, that although it is possible to disable the entire modules via the JIRA Plugin manager, we do not recommend disabling individual Tempo modules.  We cannot guarantee that the software works as expected when one or more modules are disabled.

Kind Regards,

Hlynur Johnsen

Product Manager - Tempo

Do you have plans to add a setting for this so people can do this in an offical way?

Does not seem to be possible, I get "Module cannot be modified" (Using JIRA in the cloud)

We don't use Tempo and it is a default field every time we create a new project. This is a maintence issue and our administrators spend too much time removing the default field every time a project is created.


Please allow us to remove this feature globally (on JIRA Cloud)

This is resolved for me. For future people with this issue, I found the option to do this:

Screen Shot 2017-07-17 at 9.49.48 AM.png


I've disabled Time tracking in Jira Cloud, but still see Tempo sections everywhere in stories preview and main screens :(

I Currently use Scriptrunner to hide the UI Panel for users without WORK_ON_ISSUES Permission for the project.


Scriptrunner -> Fragments -> Hide System or Plugin UI element

Hide What: 



import com.atlassian.jira.component.ComponentAccessor
def issueManager = ComponentAccessor.issueManager

def project = jiraHelper.project?.key
def user = ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser()

if (project != null){
def permissionManager = ComponentAccessor.getPermissionManager()
if(permissionManager.hasPermission(new ProjectPermissionKey("WORK_ON_ISSUES"), issue, user)){
return true
return false

Thank you @Matthew Beda this is brilliant!

We were looking for a way to disable the Tempo section in a specific project, and found your script to be a great basis to do so (by the way, Tempo have added your script and  link to here, to their documentation).

The only change we made was change the condition to the below, and it's working like a charm on Tempo v15.9.1 (Jira Server v8.20.x)

! (jiraHelper.project?.key in ["MYPROJECTKEY"])
Like Daniel Noack likes this

Go to JIRA Administration->System->Global Permissions.

Remove all the groups under Tempo Timesheets Access.

Create a new group "xyz" and add users who want to see tempo timesheets on issues.

Associate this "xyz" group to Tempo Timesheets Access.


Now tempo timesheet will only appear for users who are in the "xyz" group.

In the plug-in version (9.5.0) I used, the disabled modules are as follows:

1、System Plugin: Tempo Core -> tempo-issue-view-panel

2、Tempo Timesheets -> collaboratorsmodule

Thank you.  Can confirm Tempo Core -> tempo-issue-view-panel also works in 10.x

Pavel Junek Community Leader Nov 23, 2020

Great! Thank you

Create unique Permissions scheme for projects without Tempo.
Remove roles from permission "Work On Issues", this will hide the panel, but also hide "Log work" from Main Menu.

That worked until we upgraded to Tempo 9.3.  Now it shows:


No plans have been created for this issue.

and has a button called Plan Time.

Why on earth would they have Plan Time show up for a project that doesn't log time?  And no, we do not have the Tempo Planner Add-on.


Any idea?  I cannot find anything.

Like # people like this

Have the same problem. Upgrading from 8.x to 9.x latest and this plan time button appears and users are so confused as we don't use Tempo Planner. How do we hide the plan time from the issue screen and from the Timesheets addon itself? Anyone figure it out? 

Like Matthew Beda likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events