Forum Discussion
Defect age
Need help with calculating how much time defect sits in a particular status. If defect is submitted as New 10/2, doesn't get picked up for review until 10/10; then it moves to development on 10/20, then moves to coding on 11/2, then UAT on 11/15---basically need a way to track # of days defect is in each status that will be selected from a drop-down list. I've provided sample below. Do I need to track additional data in order to calculate this? Thanks
| Defect | Description | Status | Created on Date |
| 1234 | Something is broken | New | 9/3/2024 |
| 4321 | Something broke again | Implementation Review | 3/21/2024 |
| 4322 | Something broke again | In Development | 3/22/2024 |
9 Replies
All good now?
yes, thanks!
That sample data appears to leave a lot of things out. For one thing, although there are different codes under the heading "Defect" it's not at all clear whether we're referring in each instance to the same product, or even the same serial number of the same product. So for starters, you'd need to be more specific as to "Defect of which instance of which product".... at least two more columns.
And since the dates in your sample don't relate to the dates in your textual description, that compounds the confusion.
Do you have an actual workbook started? Is it possible for you to provide an actual copy of that actual workbook? You can post it on OneDrive or GoogleDrive with a link pasted here that grants access.
Please see if attached document provides enough detail. Basically, when defect is submitted, it's New, then once defect status changes (column G) to Implementation Review, how many days did it take, and when status changes again, how many days did it take.......Hope that makes sense. thanksmathetes
What's the relationship between "MVP" and "Defect"? I don't see a pattern that I can make sense of, not that I've spent hours trying to figure them out.
How do you propose to deal with something like the first row in that sample? And any others where "date last updated" is present? Does it supersede "Created on Date"? Why don't you create a whole new row for an update? From a design point of view, it doesn't make a lot of sense to create a single row with two transactions in it.
Could you create a newer sample showing the results you expect for a representative few of the rows, explaining those results?
