Show whether a workspace has timed out or manually stopped in usage overview
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Is your feature request related to a problem? Please describe
I am using the Gitpod usage overview to see how much time I spent on a certain task within a project. However, sometimes I manually stop a workspace and sometimes a workspace times out. This makes it harder to find out how much time I spent on a project.
Describe the behaviour you'd like
When a workspace times out I would like to be able to know if this happened so I can subtract the timeout time from the total time I spent on that project. Ideally I would see this on the usage page by showing ("Workspace timed out" and "Workspace stopped by user").
Describe alternatives you've considered
None
Additional context
N/A
Contributor guide
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
The issue names the usage overview and usage page but no files or tests. Start at the usage overview entry point and trace how workspace timeout and user-stop events are represented. Done means each workspace clearly shows whether it timed out or was stopped by the user, with coverage for both outcomes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100