Billable/Non-Billable registries in the same ticket

[Wilson Lima]

Hi guys,

Is there a way in the same ticket to register "N" entries where some are billable and some are non-billable?

Example: During the whole activity on "ticket-001", our agents registered 10 entries. Six of these were billable, and four were non-billable.

I created a custom field, Billable/Non-Billable, but once we chose one condition, it made the condition valid to the ticket itself and not to a specific entry. 

Thanks in advance.

Wilson Lima

[Fabian Lim · Accepted solution]

Hi @Wilson Lima

That's correct, the custom field apply only on the ticket.  What we have done with our clients is use a plugin either Tempo Timesheets or Activity Timeline where you can set your logs with categories for billable/non-billable.

I hope this helps.

Thanks,

Fabian

[Wilson Lima]

Thanks @Fabian Lim .

[Tomislav Tobijas _Koios_]

Hi @Wilson Lima ,

If we're talking about logged time, I can just back up what @Fabian Lim said - we also usually implement Tempo Timesheets and Tempo accounts for these cases. There are some good Tempo resources related on how to set up Tempo accounts and how to use those on issues or whenever creating new worklog:

• What are Tempo Accounts? 
• How to Get Set Up before Using Tempo Accounts 

Cheers,
Tobi

[Wilson Lima]

Thanks @Tomislav Tobijas _Koios_ .

[Gökçe Karaduman-The Starware]

Hi @Wilson Lima

Since a custom field can only store a single value per issue, it is not ideal for tracking billable and non-billable worklogs. To add extra details, such as "billable" or "unbillable" worklogs, I recommend using WorklogPRO, a third-party application available on the Atlassian Marketplace. This tool allows you to track and categorize worklogs with additional information using its attributes feature. With this feature, you can create a boolean attribute to classify worklogs as billable or unbillable. This makes it easy to analyze the billable status of worklogs by grouping them based on the attribute in either the timesheet or issue view.

Disclaimer: I work for the vendor who developed this application.