I want the managers of my company to be able to specifically see what employees are spending time on.I have been a Jira admin for about 1.5 years but haven't confronted this particular topic yet, so seeking some insight.
I considered labels and components as my choices. Between the two, I'm thinking Components would be the ideal choice, as labels (in my view) are more "relaxed" and less fundamental (and less powerful) than Components. Other than the fact that you can use Components to auto-assign issues, you can assign more than one to an issue, which is nice. Then, I will build JQL filters specifying individual components and then use Tempo to build reports with those filters.
Does anyone have experience with this? Is this a viable option? Or is there someone out there with a better solution?
What is the problem you are trying to solve with this report?
Can you clarify your goal? Are you trying to ...?
- show the time logged in Jira per user
- show time grouped by some sort of functional grouping (assigning issues to functional groups) rather than per user per issue
- come up with a method for identifying functional groupings for your issues
Do you already have Tempo installed in your instance?
Tempo is already installed.
I simply want my managers to be able to run reports that show how much time is being devoted to specific tasks.
-I want to show the time logged in Jira per user, not just by issue (or issuetype), but by specific task. I.e. we have the issuetype "Task" and the issuetype "Bug" but we have all sorts of things that those could involve, different task types (proposal writing, validation and testing, audio and video production, and then all of our products. We have at least 6 "solutions" and about 20 different products)
So I'm trying to find others who have done this and the best way to separate all of these individual tasks: Components and labels were the first thing that came to mind. I was learning toward components but I have others in Facebook suggesting a custom field since the components field is editable by users.
When choosing how to "categorize" the issue here are things to consider:
1. If you define a custom field, on Jira Admins will be able to change the list of available selections. The list can't be changed by Project Admins.
2. When using the Components field, Project Admins can change the list of available values. Non-admins (i.e. normal users) cannot change the available values, they can only select from the available values.
3. Components is a multi-select field. You could end up with your issue having more than one category selected for it, or no category selected for it.
4. Labels is a multi-select field where any user can add a new value.
If you need your managers to be able to get all the data for a category in a standard way, and across projects (Company Managed projects), then I strongly advise you to set up a custom Select List field. Then neither end users nor project admins can add or subtract from the list of available values and managers can have a list that they know is standardized across projects.
Also, you can then choose if this will be a multi-select list or a single select list, and you can choose to make it Required so that 1 and only 1 value can be specified and a value must be specified. That will mitigate trying to track time for one issue in multiple categories (if that is something you want to avoid).
It does put the burden on Jira Admins to maintain the list, but that is a price that gets paid to have standard reporting.
Hi @Everett Cavazos ,
the specific setup is highly dependent on what you want to achieve and how you would like to use it.
I would suggest the following:
1. Start with defining what reports you would like to get. This will allow you to see if the reports are easily achievable with the setup you define.
2. Make the decision how much categorizing/grouping levels you need.
3. Decide if you allow only a single category for a worklog, is this optional or mandatory, etc.
Please also remember that the more complex setup you define the more error-prone it will be. I am using many different setups and at the end of the day there are always some inconsistencies in the reports. People forget to choose the component, use wrong labels or simply do not log their worklog on time.
Hello Community! Quick disclaimer: We are running a contest on Community (The Atlympics!) from July 23rd - August 8th of 2021. If you are interested in participating in this contest (prizes! ...
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