Permissions and Limitations
The actions available for Worklog Events depend on your Jira permissions, project configuration, and Worklog source settings.
If you cannot create, edit, or delete a worklog, review the sections below to verify that the required permissions and configuration are in place.
Jira Permissions
The following Jira project permissions control which worklog actions are available.
Action | Required Jira Permission |
|---|---|
Create your own worklogs | Work on Issues |
Edit your own worklogs | Edit Own Worklogs |
Delete your own worklogs | Delete Own Worklogs |
Edit worklogs created by other users | Edit All Worklogs |
Delete worklogs created by other users | Delete All Worklogs |
If an action is unavailable, contact your Jira administrator to verify your project permissions.
Tip
Permission names may vary depending on your Jira version and project configuration.
Reporting Work for Other Users
Calendar allows you to create or edit worklogs on behalf of another user.
To do so:
you must have permission to report work for other users;
the selected user must also have permission to log work in the target project.
If these permissions are missing, the Reporter field may be unavailable or the worklog cannot be saved.
Team-managed Projects
By default, Team-managed projects do not include the Time Tracking field on issue layouts.
Without this field, worklogs cannot be created for issues in the project.
To enable worklog creation:
Open an issue in the Team-managed project.
Select More actions (⋯) > Configure.
Drag the Time Tracking field onto the issue layout.
Repeat the process for each issue type that should support worklogs.
 |
|---|
|
|---|
Note
Team-managed projects often have separate layouts for each issue type. Make sure Time Tracking is added wherever users need to log work.
Source Errors
If a Worklog source cannot be loaded because of a configuration or permission issue, an error indicator is displayed next to the source in the Left Panel.
A Worklog source with an error cannot be used until the problem has been resolved.
Common causes include:
insufficient Jira permissions;
invalid source configuration;
inaccessible Jira projects or filters.
|
|---|
Displaying Long Worklogs
One Calendar retrieves worklogs that begin shortly before the start of the currently displayed calendar period.
As a result, exceptionally long worklogs that started well before the visible period may not appear immediately, even if they overlap with the displayed dates.
For example, a worklog that:
starts on Saturday, August 9;
lasts 60 hours;
continues into the following week,
may not appear when you first open the week in which it ends.
If you navigate to the calendar period where the worklog begins and then return to the current period, the worklog is displayed correctly.
Worklog not visible in the current week.
Navigate to the previous week.
Return to the current week and the worklog is displayed.
Good to know
This behavior only affects exceptionally long worklogs that span multiple calendar periods.
Known Limitations
Keep the following limitations in mind when working with Worklog Events:
Available actions depend on your Jira permissions.
Some features may not be available for all Worklog source configurations.
Team-managed projects require additional Jira configuration before worklogs can be created.
Source configuration or permission issues can prevent worklog creation or editing.pes: task and epic.