Tempo Ideas

Very happy this is planned. I've been wanting to use this product for years, and this is feature that has prevented us from using it. I hope it's shipped soon!

We are currently experiencing a problem with the cost tracker.

We regularly correct accounts in the hours charged in Tempo by employees, assuming these changes would reflect in the cost tracker. However, the cost tracker is based on the account in the ticket, not the account on the logged hours, so corrections aren't considered, resulting in inaccurate cost tracker results.

After discussions with the Tempo team (2 weeks ago), we learned that unless the account is in the ticket, the hours won't appear in the cost tracker. Adding the account to the ticket and syncing the scop updates the cost tracker, but this requires:

1. Changing the account in the logged hours

2. Adding the account to the relevant tickets

3. Synchronizing the scops

This is too labor-intensive.

We asked if it was possible to have a filter that takes accounts based on the hours or a 'jql' in the filters. But it doesn't exist.

The Tempo team is therefore advising us to support this case in order to improve the product: we'd like cost tracking to be based on recorded time accounts, not ticket accounts.

It would be ideal to create a jql allowing this

Any update on this? Would really help the management of our cost tracker projects by being able to use the Tempo Account as the scope. For us, a Jira Project does not equal a cost tracker project.

Recently, the supported Scopes of Tempo / Cost Tracker projects has been expanded from just saved JQL Filters to also Jira Projects, Epics, and Structures.

For many of our projects, there’s a 1:1:1:1 relation between Jira Project : Cost Tracker Project : Tempo Account : Tempo Customer. There are exceptions, but for most of them the JQL filter is still one as simple as these:

• project = FOO

• Account.key = FOO

• Account.customer.key = FOO

Those filters are often not used elsewhere. They are cluttering up select boxes and lists a bit, even though we’re trying to maintain a universal naming scheme. It would therefore help if Account and Customer would also be supported scopes in Tempo Projects.

Hello everyone, thanks for your votes. We're actively looking into improving the Tempo Accounts <> Cost Tracker connection, and we'd love to learn more about how you use them together and any improvements you'd like to see.

If you have some time for a quick chat, we hope you find a slot here.

Looking forward to speaking with a few of you, and we'll keep you all posted on our development.

Thank you,
Kathryn Vargas
Tempo Product Management