JIRA's time spent calculation seems to be adding quite a few hours to actual time spent.
If I add up the columns I get a much different result than when JIRA adds up the columns.
My question: How does JIRA arrive at this amount of time tpent in the default time tracking report?
Edit: Maybe a JIRA "day" is 8 hours? That seems silly to me...
It turns out that by default 1d is not a real day, but it's a Jira day, which is 8 hours apparently.
1 day is one working day, of course. This is an issue tracking and project planning system what else could "a day"?
Also this is configurable in JIRA...
Related
I've been trying to do this for a while but can't find a solution. At work there is a special task that needs to be done daily by different people, on rotating shifts. I am trying to create a simple file in sheets in which you can go and clearly see who should be doing that tasks that day.
The data comes from a schedule that is located within the same file. Every day different people are supposed to do these tasks
So what I am trying to do is basically a formula (s) that will recognize what day is today and present it so everyone knows who is supposed to do those tasks today. This should update itself everyday, taking the data from the database. So if today is Friday 20/08/2022 it will show whatever is on the database for that date. If today is Saturday 21/08/2022 it will update and reflect what the schedule/database has.
Sounds pretty easy but I dont know where to start.
Thanks for your help!
try:
=FILTER(C:G; A:A=TODAY())
I wanna display the time spent per issue in a specific timeframe. Creating a rich filter that shows time spent is very straight forward, however, selecting the right timeframe is tricky.
Possibility #1:
resolved > -12w
That selects issues resolved within the last quarter, but then all time is displayed, even when the issue is is much older and a lot of time has been booked more than 12 weeks ago.
Possibility #2:
created > -12w
That selects issues created within the last quarter, and automatically excludes issues that are still being worked on but are older
Possibility #3
created > -12w and resolved < -4w
That selects issues created and resolved and disregards issues going between timeframe boundaries.
Possibility #4
worklogdate > -12w and worklogdate < -4w
That would select only issues with correct worklog dates, i.e., issues that REALLY have been worked on in that timeframe, but when I then analyze worklogtime or time spent, that is still all the time worked on the issue, not just the time within the specified timeframe.
Any idea how I could achieve showing the time spent per issue of a very specific timeframe?
First-time caller, long-time listener. I'm sorry if the title is a bit off, not really sure how to vocalize this issue. I have built a system at work for our work-study students to clock-in on. Unfortunately, the rest of our University is on a paper system and I cannot accept that. The system is made from two parts. The first part is a Google form where clock-in information is reported, it also includes a filter that separates that information based on pay period. The second is another sheet that imports that data and formats it into a printable timecard.
Here is the problem in a nutshell. We have students that work past midnight, potentially to 2:00 am. I need this system (or some system) to clock them out at midnight and clock them back in on the following day at 12:00 am.
Not even sure where to start with this one. I guess I need a script? A solution, advice or just a point in the right direction would be greatly appreciated. Thanks for your time all!
Form & Filter:
https://docs.google.com/spreadsheets/d/19LfKUQY6etiRY2wuyFYM8Jzay7IGXrwn0rHKgDwnmE4/edit?usp=sharing
Pay info and Timecard format:
https://docs.google.com/spreadsheets/d/1-2-7D7AHi6J-4cURlOsQOC1KznCR6zsejkTbyBFamjA/edit?usp=sharing
It sounds like a cool project! Here are some thoughts:
Using the Script Editor at Tools > Script Editor in Google Sheets:
You can collect the clock in and clock out timestamps.
You go through those cells in the code and if the day is different in between Clock in and Clock out, we know the student worked overnight. Now you do this:
You take the clock in time and make the clock out time midnight on that day.
You insert a new row after the Clock in row (sheet.insertRow()), and then in the new row you set the Clock In time to 0AM and the Clock Out time to the departure time.
I imagine people have already done this before and faced your same problem, so here are some examples I found online, although they may not address your specific issue:
https://bazroberts.wordpress.com/2017/03/06/apps-script-clocking-in-out-system/
You may be able to find a Google Sheets add-on for this - I see a couple on the store: https://docs.google.com/spreadsheets/create?addon_store
This might point you in the right direction. I check for a PM followed by AM. If it finds this condition, it splits it into two calculations. One up to midnight and the other on for after midnight. The next day looks back and if after midnight time occurs it picks it up. If no after midnight time occurs, it does what you do now. I think you can make this work (you will need to add a couple of columns which you can hide). I don't know what you would do on the last day of your time card. Below is an example you can copy:
https://docs.google.com/spreadsheets/d/1cO1ggY05kz70lfPE0YZCXaaa0AiaGKDM1s9FQPnw6Zs/edit?usp=sharing
I want to specify the team capacity per user and per activity on TFS'12 Scrum Template 2.0, which may differ on every day on the sprint.
As described in http://msdn.microsoft.com/en-us/library/ee191595.aspx I can set capacity per day of a person, like 7 hours for a sprint of 5 days.
How can I specify a capacity like the one below?
Day 1 : 7 hours
Day 2 : 5 hours
Day 3 : 9 hours
Day 4 : 3 hours
Day 5 : 6 hours
Thanks.
As others have mentioned, the TFS capacity planning doesn't support this. You can use the "Days off" to block off entire days, but not parts of a day.
That being said, the capacity planning is used to try to know how much work is assigned to an individual or team and whether you have enough capacity left to address the work remaining. For the majority of your sprint, an average will work. For risk-averse managers, you may want to put in the minimum amount and just use the additional hours as bonus that is not part of the capacity.
In your specific example, however, if your individual is averaged to 6 hours a day, you'll get a capacity that starts hurting you at the end of your iteration. It will look like you have 12 hours left for Day 4 and 5, but really you only have 9 hours.
If you use the minimum approach, you'll average at 3 hours a days and look like the capacity is full part way through Day 3 if you assign tasks that fill up their actual hours.
This is one of the reasons that you should be trying to get a consistent availability from your team, and not just having an hour here or there being added to the sprint. 100% allocation, ideally, as you'll read about on most anything written on scrum/agile teams.
In the end, also, you need to ask yourself what you are going to use the capacity numbers for. That will dictate whether this is the right tool for what you need to accomplish, and also what approach you can take.
It is not possible to set the capacity on a daily basis (unless of course, you have a 1 day sprint). The easiest solution would be to find the average availability and put that in for the individual's capacity.
Generally speaking however, individual capacity isn't what is important in Scrum, the Team's capacity & velocity are.
If you want to have this level of detail in your planning, I'd suggest to setup Project Server Integration
PLEASE SEE THE EDIT BELOW, THE REPORT SEEMS TO USE CACHED DATA?
I cant figure out why there are 89 hours of work remaining, when I have 3 Active Work Items totaling 44 hours:
My Burndown Chart:
Remaining hours on 3 blocked tasks equals 44 hours:
I do set the completed hours when I close my tasks:
What am I doing wrong with the remaining vs completed hours? is this a bug in TFS?
This seems to be different to previous experiences, I've just started a new job.
EDIT:
Today the report is correct, how do I stop the caching happening?
This burndown report reads from the cube and not from the operational datastore. The cube is processed every 2 hours.