[Bug]: Auto-settle inactivity setting appears as a top-level option
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 23k
- Forks
- 5.9k
- Avg merge
- 11h 14m
- Merged PRs (30d)
- 357
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/web
Steps to reproduce
- Open Settings.
- Open the General settings panel.
- Enable Auto-settle inactive threads.
- Compare Days of inactivity before auto-settle with its parent toggle and with the existing Start from origin child setting.
Expected behavior
Days of inactivity before auto-settle should be visually presented as a child of Auto-settle inactive threads.
Actual behavior
The inactivity-days row uses the default settings-row styling, so it appears to be an unrelated top-level setting.
Impact
Cosmetic issue
Version or commit
main before #7093
Environment
Web and desktop clients using the shared web settings UI.
Logs or stack traces
Not applicable.
Screenshots, recordings, or supporting files
Not applicable.
Workaround
The dependency is still functional, but users must infer the relationship from the control appearing only after the parent toggle is enabled.
Implemented in #7093.
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
Start in apps/web by tracing the General settings panel and the existing "Start from origin" child setting, using the shared web settings UI described in the issue. Compare the styling of "Days of inactivity before auto-settle" with its parent toggle and that child setting. Done means the row is visually presented as a child of "Auto-settle inactive threads" while preserving the existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100