Filtering functionalities for Temporal UI
Nobody has claimed this yet.
- 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.
The event history usually contains a lot more than I need and I need to filter the events based on some criteria e.g. message like {regex_1} or activityName like {regex_2} or a combination of both. Or activityName not like {regex_3}
This would hugely improve readability of the temporal UI. Also need features like default filters that can be at user-level or namespace level, etc.
Describe the solution you'd like
Advanced filtering for event history in compact & history modes. Description in above heading.
Describe alternatives you've considered
Not applicable
Additional context
Not applicable
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Temporal UI event history in compact and history modes. Define how message and activityName filters, combinations, negation, and user- or namespace-level defaults should work, then confirm the expected behavior with maintainers. Done means advanced filtering is available in both requested modes with documented filter semantics.
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
- Mostly clear
- Newbie friendliness
- 35/100