Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Tempo accounts and categories

There is a one to many relation for customers to accounts, but only a one to one relation between accounts and categories? What is the use of this, I want to set up a structure like Customers has many accounts and account has many categories (f ex Build cost vs Run cost) I then want to be able to separate the build and run cost per account, but currently the only way to do this is create 2 separate accounts with same description and different category which then will not be summed up at account level as they are split. Any way to solve this,

4 answers

1 accepted

0 votes
Answer accepted

Hi Chris,

The original idea was to classify accounts into types. That is how we have used them at TM Software. We have different categories like "Service Agreement", "Fixed Contract", "Training", etc. This allows us to report on different types of engaments.

You use case is quite different as you want to classify each worklog in the same account. This makes the account category relation unsuitable to you. Instead, you can add a dynamic worklog attribute with the possible values for each worklog.

We are thinking about how to solve this better and maybe we can extend the categories to be more flexible, or add a new "work type" classification on a worklog level.

Thanks for the feedback and I hope the dynamic worklog attribute feature solves your use case until we have a better solution.

Cheers,
Viðar
TEMPO

This is exactly what i have done, i have set up the account in as attribute in the worklog for the relevant project. That will do for now.

Thank you for the quick reply

Does this work with Jira Tempo time tracking?

Hi Mike,

 

Thanks for your contact. Contractspro Cloud does not have integration with Tempo. It has its own time tracking system. We are working on New features to be released soon. You can check the roadmap on mindproapps.com/roadmap.

Regards,

Eduardo

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you