Your client work and internal work aren’t the same. Your time-tracking fields don’t need to be either.
If your Jira instance contains both, you’ll know the problem.
Client teams need details such as billable status and account codes, while internal teams don’t want to answer billing questions every time they log work.
Until recently, worklog attributes in Clockwork Pro applied across every project.
Add a field for one team and it appeared….(you guessed it)….for everyone.
Teams could leave it optional, ask people to ignore it, or chase missing details at month-end.
Now, each project can ask for the details it actually needs.
With project-level worklog attributes in Clockwork Pro, you can tailor the fields people see when logging time:
- Add attributes that apply only to that project.
- Keep or hide attributes inherited from the global setup.
- Make supported fields required where the information matters.
Worklog attributes are set per project: inherit the global ones you want, ignore the rest, and add attributes only this project needs.
A client project might capture billable status, account and overtime. An internal project might capture cost centre or CAPEX/OPEX instead, without showing billing fields.
Project Leads and Jira Admins can now configure this in Clockwork Pro’s project settings.
The aim is simpler time logging for teams and more useful data for reporting.
Read the full breakdown and configuration guide or try Clockwork Pro for free for yourself.
How does your team keep time logging simple while collecting the details finance and project managers need?
