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?
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())
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
Recently I started to notice that we somehow have resolved more tickets than we've created. Since it seems paradoxical I can only come to two conclusions:
There is a bug in JIRA.
I don't understand what it is actually graphing.
…or both, I suppose. Here is a screenshot of a graph from this morning:
(The filter that is being graphed is a custom filter. I don't know if that's relevant.)
Is there an explanation for this beyond just "lol JIRA"?
This chart shows that your project has
71 issues that are unresolved and have a creation date within the given time period
79 issues that are resolved and have a resolved date within the given time period
It tells you that your stock of unresolved Issues has decreased by 8 between 22 Mar and 1 Apr.
Non-cumulative would show you a non-zero value only for the days where at least one issue has been created (red) or resolved (green).
From my point-of-view nothing to worry about. Projects mostly start with more issues created than resolved and work themselves into a good balance. Having resolved more than being created just means you have fixed several open issues and either not found new errors while testing or have not tested at all.
I have been using TFS to track my backlog items and I am now trying to write a query to see how long I took on particular tasks in the last 7 days. So Far I have this query:
Work Item Type = Task
AND State = Done
AND Closed Date = #Today - 7
AND Area Path = #Project
AND Assigned To = #Me
and have added the column "Closed Date" which shows the time work stopped on this item. But I cannot get any information as to when work started on the Task
Feels like the data should be there as on particular tasks it has the following kind of information:
Is this possible? I don't mind extracting the data to Excel to analyse.
The reason I ask is because I would then like to go on to compare the amount of hours assigned to a particular task and compare it to amount of hours actually taken to help my predictions of time taken in future.
It's a pretty simple query actually.
Here's what I'm using.
(Work Item Type = User Story
OR Work Item Type = Bug
)
AND State <> New
AND State <> Removed
Simply include the Activated Date, the Resolved Date, and the Closed Date in the displayed columns. The time between Activated and Closed is your total cycle time.
My team uses Resolved as a "pending deployment" status, so comparing Resolved to Closed allows us to determine how long it takes to get an item from "done" to "in prod".
TFS is not intended to be a time tracking tool. You could query the work item history with the TFS API and check the timestamps on when the state transitions occurred if you really wanted to.
Agile projects don't focus on how long individual tasks take -- they focus on how much value the development team is providing over the course of a set period of time. One thing might be estimated low, one task might be estimated high, but it ultimately doesn't matter as long as the team delivers what they committed to deliver.
It's a good practice to track Cycle Time for a team to discover areas for improvements (for User Story level, yes)
It's not good that user must go Excel to calculate Cycle Time. I can't use diagram Azure Devops tools with this calculations and its not automated.
Cycle Time widget don't shows results for several teams and it's not flexible tool, so it's not enough
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...