temporalio / temporalio/ui

Time range selection for workflow history graph

Open
#3,161 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
431
Forks
179
Avg merge
2d 9h
Merged PRs (30d)
71

Description

Is your feature request related to a problem? Please describe.

Long running workflows that execute multiple operations in a short burst and then wait for longer time are hard to view on the history graph; All events are visually "compressed" and put so close to each other that it is hard to see any relations between them.

Describe the solution you'd like

Option to select time range of events that should be displayed on the history graph.

Describe alternatives you've considered

"Filter" button could give option to set start/end time of events displayed on the graph (similar to workflow list filtering).

Additional context

Other "nice to have" features:

  • automatic "compression" of inactivity periods on the graph - instead of drawing long empty space between events it could look like this: two vertical lines with text "2h" between them
  • "sliding window" view - graph view is configured to show time window (for example 30m) and scroll bar on the graph can be used to move the window left/right.
  • draw timestamps on top of the graph (or allow drawing events from top to bottom, so latest events are closer to timestamps), especially in "minimized" mode - if I want to check when the latest event happened i have to scroll the graph to see the related timestamp.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names the workflow history graph and refers to the existing workflow list filtering as a possible model, but it names no files, tests, or entry points. Start by locating the graph and filtering UI, then define how a selected start and end time should affect displayed events. Done means users can select a time range and the graph shows only events within it.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.