Worklog attributes let you capture extra details on Jira worklogs so your team can track time with more context. Instead of logging only time spent, users can also record information like whether time is billable, which customer the work was for, what activity was performed, or which cost center applies.
Worklog attributes in Clockwork Pro can be configured globally and overridden for specific projects or spaces so different teams can capture different kinds of time data.
What are worklog attributes?
Worklog attributes are additional fields added to the worklog form. They help teams collect structured data alongside time entries without creating separate Jira custom fields for every use case.
Common examples include:
-
Billable vs non-billable time
-
Customer or account name
-
Activity type
-
Cost center
-
CAPEX vs OPEX classification
-
Work location or overtime flag
Attributes are especially useful when you want better reporting, filtering, grouping, or billing insight from your timesheets.
What types of worklog attributes are available?
Clockwork supports three attribute types for worklogs:
-
Checkbox — best for yes/no values such as Billable
-
Single select dropdown — best when users should choose one option from a list, such as Customer or Request Type
-
Labels — best when users may need one or more flexible tags, such as Activities, Cost Centers, or internal classifications
Depending on the attribute type, administrators can define options, set default values, decide whether the field is mandatory, and control whether users can create new values.
How do administrators add worklog attributes?
To add global worklog attributes:
-
Log in as a Jira administrator.
-
Go to Jira Settings > Apps > Clockwork Configuration.
-
Open the Worklog Details tab.
-
Use the Add new attribute dropdown and choose the attribute type.
-
Complete the attribute settings.
-
Save the configuration.
Once saved, the new attributes appear in the worklog dialog for the relevant projects or spaces.
Clockwork Pro also supports more advanced worklog detail configuration, including making the worklog description mandatory for manually created worklogs.
Can worklog attributes be different for different projects?
Yes. Clockwork supports global configuration and project-specific configuration. This means teams do not have to use one rigid set of fields everywhere.
For example:
-
A client project might need Billable, Customer, and Overtime
-
An internal project might need Cost Center and Work Location
-
A support team might need Request Type or Activity
Specific project or space settings can inherit global attributes, ignore some of them, or add their own.
Where do users see and fill in worklog attributes?
Users see worklog attributes when creating or editing manual worklogs in Clockwork or when they stop a timer. Attributes can also be visible when reviewing worklog details in places like the work item view, calendar, or the timesheet worklog detail view.
How do worklog attributes help with reporting?
Worklog attributes become useful reporting dimensions. Teams can use them to filter and break down timesheets and reports in more meaningful ways than issue, user, or project alone.
Examples of reporting use cases:
-
Filter for only billable hours
-
Group time by customer across multiple projects
-
Analyze how much time is spent on different activities
-
Separate internal overhead from client delivery work
-
Track time by cost center, funding source, or operational category
The real value of worklog attributes is not just capturing more data. It is capturing the right data in a structured way so teams can make better operational, financial, and planning decisions later.
What are some best practices for setting up worklog attributes?
-
Start with a small number of high-value attributes rather than too many fields
-
Use a checkbox for simple binary questions like billable/non-billable
-
Use single select dropdowns when consistency matters for reporting
-
Use labels when you need flexibility or users may apply multiple values
-
Make fields mandatory only when the information is truly required
-
Review attribute options periodically to remove duplicates or outdated values
A good rule of thumb is to collect only the information your team will actually use in reports, billing, budgeting, or operational review.
Frequently asked questions