Charting
Charting
How To Calculate Time In Status?
I want to calculate time in status or time difference for "IN QA/REVIEW" which stops being in the status when it transition to either to "IN QA/REVIEW" / "Failed QA" / "Verified (Ready to Deploy)". Is there a known approach that DOMO offers that can solve this challenge?
Status | Timestamp |
|---|---|
Verified (Ready to Deploy) | 2024-01-03T14:32:45 |
IN QA/REVIEW | 2023-12-19T14:48:52 |
READY FOR QA | 2023-12-18T22:49:23 |
In Code Review | 2023-12-18T19:56:53 |
In Progress | 2023-12-15T03:09:07 |
In Code Review | 2023-12-14T03:52:11 |
In Progress | 2023-12-13T22:02:54 |
Failed QA | 2023-12-13T22:02:48 |
IN QA/REVIEW | 2023-12-13T19:43:05 |
READY FOR QA | 2023-12-13T19:32:07 |
In Code Review | 2023-12-13T17:49:31 |
In Progress | 2023-12-13T17:49:29 |
Failed QA | 2023-12-13T17:49:28 |
IN QA/REVIEW | 2023-12-13T17:49:26 |
READY FOR QA | 2023-12-13T17:48:59 |
In Code Review | 2023-12-04T16:28:10 |
In Progress | 2023-11-29T15:56:31 |
To-Do | 2023-11-29T15:56:29 |
Best Answer
-
I was able to resolve it using a card
Rank and Windowand LAG 1 to have a new column with next status timestamp.I also added same LAG 1 for the next status name so I can see which status is going after IN QA status.
Thank you again
0
Answers
-
I would recommend pivoting out your data in an ETL so that you have a row for each status. You can then calculate the difference between each status/step by subtracting the 2 columns.
David Cunningham
** Was this post helpful? Click Agree 😀, Like 👍️, or Awesome ❤️ below **
** Did this solve your problem? Accept it as a solution! ✔️**0 -
Thank you, David for your quick response. Is there a way to Pivot on per-ticket \ per In-QA status basis? I am not sure how the ranking will happen if I Pivot since one ticket may have multiple transitions from "In QA".
Ticket
Status
Timestamp
JIRA-3
Verified (Ready to Deploy)
2024-01-03T14:32:45
JIRA-3
IN QA/REVIEW
2023-12-19T14:48:52
JIRA-1
Failed QA
2023-12-13T22:02:48
JIRA-1
IN QA/REVIEW
2023-12-13T19:43:05
JIRA-2
Verified (Ready to Deploy)
2023-12-15T18:49:28
JIRA-2
IN QA/REVIEW
2023-12-14T17:49:26
JIRA-2
Failed QA
2023-12-13T17:49:28
JIRA-2
IN QA/REVIEW
2023-12-13T17:49:26
I want to calculate how long it takes to transition per
Ticketfrom StatusIN QA/REVIEW→[Failed QA \ Verified (Ready to Deploy)]. One ticket may have 2 transitions like for JIRA-2, where status transitioned first intoFailed QAand secondVerified (Ready to Deploy).0 -
I was able to resolve it using a card
Rank and Windowand LAG 1 to have a new column with next status timestamp.I also added same LAG 1 for the next status name so I can see which status is going after IN QA status.
Thank you again
0
Categories
- All Categories
- 2K Product Ideas
- 2K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 311 Workbench
- 7 Cloud Amplifier
- 9 Federated
- 3K Transform
- 114 SQL DataFlows
- 654 Datasets
- 2.2K Magic ETL
- 4.1K Visualize
- 2.5K Charting
- 807 Beast Mode
- 80 App Studio
- 44 Variables
- 761 Automate
- 189 Apps
- 480 APIs & Domo Developer
- 75 Workflows
- 17 DomoAI
- 40 Predict
- 17 Jupyter Workspaces
- 23 R & Python Tiles
- 408 Distribute
- 119 Domo Everywhere
- 279 Scheduled Reports
- 10 Software Integrations
- 141 Manage
- 137 Governance & Security
- 8 Domo Community Gallery
- 47 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 114 Community Announcements
- 4.8K Archive