How To Calculate Time In Status?

Vova
Vova Member
in Charting

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

  • Vova
    Vova Member
    edited June 20 Answer ✓

    I was able to resolve it using a card Rank and Window and 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

Answers

  • david_cunningham
    david_cunningham Coach

    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! ✔️**

  • Vova
    Vova Member
    edited June 20

    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 Ticket from Status IN QA/REVIEW → [Failed QA \ Verified (Ready to Deploy)]. One ticket may have 2 transitions like for JIRA-2, where status transitioned first into Failed QA and second Verified (Ready to Deploy).

  • Vova
    Vova Member
    edited June 20 Answer ✓

    I was able to resolve it using a card Rank and Window and 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

Categories