Hub
Pricing About
WorkflowWorkflow

JKISeason4-12

JKISeason4-12
hanantoprabowo profile image
Draft Latest edits on 
Jul 31, 2025 5:08 PM
Drag & drop
Like
Download workflow
Workflow preview

Challenge 12 - Measuring Ticket Processing Time

Level: Medium

Description: Imagine you are managing your team's work using a Kanban board to track progress. On the board, there are tickets for different tasks and each ticket can move from one stage to the next, as work progresses. Each ticket has a unique ID, the date the ticket was created, the date of the move, and the “from” and “to” stages of the move. Typically, tickets move across different stages in this sequence: "New" → "Doing" → "Review" → "Done". Occasionally, tickets can move backwards (from "Review" → "Doing", if edits need to be made) or are not always created in the "New" stage. As the manager of the team, you always strive for better and more efficient ways to manage tickets. You are especially interested in uncovering how much time, on average, tickets spend in stage “Doing”. Understanding this could reveal bottlenecks and improve your team’s efficiency.

To answer the question, you decide to build a solution that reads the data, tracks each ticket’s time in stages, and zooms in on the "Doing" stage. Keep in mind, though, that you should not include tickets that are stuck in the "Doing" stage, as there is no way to know how long they will stay there for. Ready to uncover what’s really happening by calculating the average number of days tickets spend in "Doing"?

Beginner-friendly objectives: 1. Read the ticket movement data from a CSV file. 2. Convert string columns to date format, and lag the Move date column. 3. Compute how many days each ticket spends in each stage. 4. Focusing only on the "Doing" stage, calculate the average number of days tickets spend in this stage.

Intermediate-friendly objectives: 1. Notice that some tickets have visited the "Doing" stage more than once. Before computing the average number of days tickets spent in "Doing", make sure that tickets that have visited the "Doing" stage multiple times get properly accounted for as a single ticket.

External resources

  • Ticket Data on KNIME Community Hub
Loading deploymentsLoading ad hoc jobs

Used extensions & nodes

Created with KNIME Analytics Platform version 5.5.0
  • Go to item
    KNIME Base nodesTrusted extension

    KNIME AG, Zurich, Switzerland

    Version 5.5.0

    knime
  • Go to item
    KNIME ExpressionsTrusted extension

    KNIME AG, Zurich, Switzerland

    Version 5.5.0

    knime
  • Go to item
    KNIME JavaScript ViewsTrusted extension

    KNIME AG, Zurich, Switzerland

    Version 5.5.0

    knime
  • Go to item
    KNIME JavasnippetTrusted extension

    KNIME AG, Zurich, Switzerland

    Version 5.5.0

    knime
  • Go to item
    KNIME Math Expression (JEP)Trusted extension

    KNIME AG, Zurich, Switzerland

    Version 5.5.0

    knime
  • Go to item
    KNIME Quick FormsTrusted extension

    KNIME AG, Zurich, Switzerland

    Version 5.5.0

    knime
  • Go to item
    KNIME ViewsTrusted extension

    KNIME AG, Zurich, Switzerland

    Version 5.5.0

    knime

Legal

By using or downloading the workflow, you agree to our terms and conditions.

KNIME
Open for Innovation

KNIME AG
Talacker 50
8001 Zurich, Switzerland
  • Software
  • Getting started
  • Documentation
  • Courses + Certification
  • Solutions
  • KNIME Hub
  • KNIME Forum
  • Blog
  • Events
  • Partner
  • Developers
  • KNIME Home
  • Careers
  • Contact us
Download KNIME Analytics Platform Read more about KNIME Business Hub
© 2025 KNIME AG. All rights reserved.
  • Trademarks
  • Imprint
  • Privacy
  • Terms & Conditions
  • Data Processing Agreement
  • Credits