You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
we need to implement a classification of jira worklogs for reporting.
some example reports may be:
* distinguish between billable and not billable hours,
* hours spent according to activities (analysis, development, testing, ...),
* hours spent on bugs reported by customers vs. found internally
* hours covered by a contract (internal hours, covered by contract, not covered but paid, covered and unpaid)
that's why we need to classify the worklogs in more dimensions.
for the activities (analysis, design, implementation, testing, ...) we plan to use attributes (tempo work attribute or issue custom field).
for the other reports we need to distinguish whether the work is paid by the customer or is internal. we have come with 2 solutions:
1. distinguish the type of work by the issue type (e.g. Bug/Incident is internal cost, support activities are paid, work on change requests is paid, ...), which implies to have multiple issue types (> 10) in every project
2. distinguish the type of work by custom field attributes in combination with issue type
we're not in agreement which one would be better for us, so i'd like to hear your opinions and arguments on what solution you'd prefer or which approach did you choose for similar use case.