Customers have hours that they purchase ahead of time to be used for various tasks, each "bucket" of hours is given a project number in Jira. We want to know how many hours have been used and how many hour are left for various customers. What is the easiest way to do this?
@Elizabeth Paredes The scenario you describe is handled quite well by Tempo Timesheets - as another user mentioned above.
You can log time on various Jira issues, but additionally, you can create accounts for your clients or projects. Accounts easily consolidate time across multiple Jira issues and Jira projects for you to make invoicing and/or tracking service contract hours much easier.
Customers can have multiple accounts depending on projects or contracts but an account is associated with one customer.
I don't know of another app that can track and consolidate worklogs out of the box across multiple issues and projects in Jira.
You can read more about Tempo accounts here:
https://www.tempo.io/blog/a-quick-and-easy-introduction-to-tempo-accounts
You can also reach out to Tempo sales for a demo.
Rob Huntley
Tempo Product Expert
Hi @Elizabeth Paredes ,
welcome to the Atlassian community!
My suggestion is to use Tempo for JIRA app ( https://marketplace.atlassian.com/apps/6572/tempo-timesheets-jira-time-tracking?hosting=cloud&tab=overview ) that allow you to manage all this aspects in a simple way.
Hope this helps,
Fabio
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the Atlassian Community!
I'm Leo, Product Manager of Projectrak.
Projectrak allows you to create project properties (similar to issue fields). How can it help you? You can use 3 properties to know how many hours are left in a project:
The result of this configuration will be something similar to this one:
Hope it helps you!
Please let me know if you need any help!
Leo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Elizabeth Paredes -- Welcome to the Atlassian Community!
Possible suggestions depend upon what you consider an "easy way" and how you are representing the project number and various tasks. I believe you need to provide more information for the community to offer ideas.
For example...do you have all of your tasks stored in one-and-only-one Jira Project and you have some issue field to identify project number?
Or...are your projects (project number) parent items to the tasks, such as a Jira Epic?
Or...are your projects (project number) each an independent Jira Project? And so on...
Also, I recommend having a discussion with your Jira Site Admin to explain this scenario to see what they think.
Thanks, and kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.