Document toolboxDocument toolbox

This article is for Timesheets for Cloud. Visit Data Center

Troubleshooting Worklog Editing

Having trouble editing worklogs? Below you can find a list of common reasons why you may not be able to edit your own or all worklogs in Tempo Timesheets.

Issue Not Editable

Jira allows administrators to define workflow states where issues cannot be edited. All Issues and associated worklogs in this state cannot be edited. In order to edit worklogs not editable for this reason:

  • As a Jira user

    • Try transitioning the issue to an editable status in the workflow (for example, from Closed to Reopened).

  • As a Jira Administrator

    • Edit the Jira workflow status and set the 'Issue.editable' property as true.

You Lack Permission to "Work On Issues"

If you have this permission for at least one project, you can access Tempo Timesheets. You cannot create worklogs for issues in other projects for which you do not have this permission.

  1. To grant this permission to users, as a Jira Administrator, open the Project Permission Scheme for the project.

  2. Grant the users permission to Work On Issues. See also Managing project permissions in Atlassian Jira's documentation.

You Lack Permission to "Edit Own Worklogs"

Jira Administrators use this permission to control if users can edit their own worklogs or not. To allow users to edit their own worklogs:

  1. As a Jira Administrator, open the Project Permission Scheme for the project in question.

  2. Grant the user in question permission to Edit Own Worklogs. See also Managing project permissions in Atlassian Jira's documentation.

You Lack Permission to "Edit All Worklogs"

Jira administrators use this permission to control which users can edit all worklogs within a particular project. To allow users to edit all worklogs within a project:

  1. As a Jira Administrator, open the Project Permission Scheme for the project in question.

  2. Grant the user in question permission to Edit All Worklogs. See also Managing project permissions in Atlassian Jira's documentation.

You Lack Permission to "Log Work for Others"

Jira administrators use this permission to control which users can log work for other users within a particular project. You might be able to edit your own worklogs, but you need this permission to edit worklogs from other users.

  1. As a Jira Administrator, open the Project Permission Scheme for the project in question.

  2. Grant the user in question permission to Log Work for Others. See also Managing project permissions in Atlassian Jira's documentation.

Week Is Closed

Tempo enables Tempo administrators to automatically schedule week closure within an Open Period using the Tempo Scheduler. To edit worklogs currently not editable for this reason:

As a user with the Approve Timesheet permission, give the user in question a Grace Period.

User Timesheet Is Not Open

If the Timesheet has already been approved or is pending approval, underlying worklogs cannot be edited. To edit worklogs currently not editable for this reason:

As a user with the Approve Timesheet permission:

  • In the case of Approved Timesheets, re-open the timesheet.

  • In the case of Timesheets Pending Approval, reject the timesheet.

Period Is Closed

Tempo enables Tempo Administrators to control when users can log time on issues. This is configured using Period management. To edit worklogs currently not editable for this reason:

As a Tempo Administrator, open the period in question from the Period management page.

Account Has Been Closed

Tempo account administrators might close accounts that users may no longer log time on. To edit worklogs that are associated with closed accounts, do one of the following tasks:

  • As a Tempo account administrator, re-open the account.

  • As a Jira administrator, select the checkbox for the following setting on the Tempo configuration page: Users can log work for closed and archived accounts.

Are you seeing discrepancies in the time stamps for your worklogs? If so, please see Why is there a time difference between my Jira worklog and my Tempo worklog.